HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: ldd shows "Unresolved symbol" for libpthread.s...
Operating System - HP-UX
1833187
Members
3274
Online
110051
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2007 05:09 PM
03-06-2007 05:09 PM
ldd shows "Unresolved symbol" for libpthread.sl
Hi,
Do I have a faulty installation of my system when ldd gives me the following output?
/usr/lib>ldd libpthread.sl
/usr/lib/dld.sl: Unresolved symbol: symbol not found: __errno (libpthread.sl)
I have:
lrwxr-xr-x 1 root root 21 Feb 1 2006 libpthread.sl -> /usr/lib/libpthread.1
and did:
/usr/lib>what libpthread.sl
libpthread.sl:
Pthread Interfaces
$Revision: libpthread.1: @(#) depot-32pa R11.11_BL2003_1209_2 PATCH_11.11 PHCO_29960 Tue Dec 9 01:51:37 PST 2003 $
/usr/lib>what libpthread.1
libpthread.1:
Pthread Interfaces
$Revision: libpthread.1: @(#) depot-32pa R11.11_BL2003_1209_2 PATCH_11.11 PHCO_29960 Tue Dec 9 01:51:37 PST 2003 $
Thanks,
Joost
Do I have a faulty installation of my system when ldd gives me the following output?
/usr/lib>ldd libpthread.sl
/usr/lib/dld.sl: Unresolved symbol: symbol not found: __errno (libpthread.sl)
I have:
lrwxr-xr-x 1 root root 21 Feb 1 2006 libpthread.sl -> /usr/lib/libpthread.1
and did:
/usr/lib>what libpthread.sl
libpthread.sl:
Pthread Interfaces
$Revision: libpthread.1: @(#) depot-32pa R11.11_BL2003_1209_2 PATCH_11.11 PHCO_29960 Tue Dec 9 01:51:37 PST 2003 $
/usr/lib>what libpthread.1
libpthread.1:
Pthread Interfaces
$Revision: libpthread.1: @(#) depot-32pa R11.11_BL2003_1209_2 PATCH_11.11 PHCO_29960 Tue Dec 9 01:51:37 PST 2003 $
Thanks,
Joost
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2007 05:56 PM
03-06-2007 05:56 PM
Re: ldd shows "Unresolved symbol" for libpthread.sl
>Do I have a faulty installation of my system when ldd gives me the following output?
No, it is illegal for you to use that command and expect it not to have those unsats. __errno is defined in libc.
What is your real problem?
The latest libptread patch is PHCO_33282.
No, it is illegal for you to use that command and expect it not to have those unsats. __errno is defined in libc.
What is your real problem?
The latest libptread patch is PHCO_33282.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2007 06:42 PM
03-06-2007 06:42 PM
Re: ldd shows "Unresolved symbol" for libpthread.sl
Dennis,
My problem is the integration of Sybase and Tuxedo libraries (for HP-UX 11.11) in a single shared library (to be used by the Sybase e-Biz Impact engine).
At run-time the following messages are logged:
082857.hqbrl02!?proc.17546.7.1: GP_CAT:1346: ERROR: pif: can't get address for EntryPoint '_ep_dl_instantiate' (impl 'registry.sl')
082857.hqbrl02!?proc.17546.7.1: GP_CAT:1346: ERROR: pif: can't get address for EntryPoint '_ep_dl_instantiate' (impl 'registry.sl')
0
I expect the problem to be in the Tuxedo area or the way I compile/link but I am not sure.
The Tuxedo Administrator took a look at my system (of which I am not root but developer) and noticed that ldd gave this error. He tried it at his own HP-UX box and the error was not shown. His conclusion was that I had a "not-well-maintained" system.
Regards,
Joost
BTW, I do not really understand your answer about 'the command being illegal for me'. If __errno is specified in libc, why does ldd mention it?
My problem is the integration of Sybase and Tuxedo libraries (for HP-UX 11.11) in a single shared library (to be used by the Sybase e-Biz Impact engine).
At run-time the following messages are logged:
082857.hqbrl02!?proc.17546.7.1: GP_CAT:1346: ERROR: pif: can't get address for EntryPoint '_ep_dl_instantiate' (impl 'registry.sl')
082857.hqbrl02!?proc.17546.7.1: GP_CAT:1346: ERROR: pif: can't get address for EntryPoint '_ep_dl_instantiate' (impl 'registry.sl')
0
I expect the problem to be in the Tuxedo area or the way I compile/link but I am not sure.
The Tuxedo Administrator took a look at my system (of which I am not root but developer) and noticed that ldd gave this error. He tried it at his own HP-UX box and the error was not shown. His conclusion was that I had a "not-well-maintained" system.
Regards,
Joost
BTW, I do not really understand your answer about 'the command being illegal for me'. If __errno is specified in libc, why does ldd mention it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2007 07:04 PM
03-06-2007 07:04 PM
Re: ldd shows "Unresolved symbol" for libpthread.sl
>At run-time the following messages are logged:
082857.hqbrl02!?proc.17546.7.1: GP_CAT:1346: ERROR: pif: can't get address for EntryPoint '_ep_dl_instantiate' (impl 'registry.sl')
It seem you want to look for _ep_dl_instantiate?
>He tried it at his own HP-UX box and the error was not shown. His conclusion was that I had a "not-well-maintained" system.
I just now tried it and I don't get that message for your version of libpthread either. About the only differences are in the versions of ldd that you and admin have. What are they?
I have B.11.53, PHSS_33035. While installing this may fix ldd, I'm not sure it will fix your Tuxedo issue, but it can't hurt. At least find out what your admin has.
The latest dld patch is PHSS_35381.
>I do not really understand your answer about 'the command being illegal for me'.
Without a close look, it seems to me you are debugging something like:
$ echo "Unresolved symbol:"
It prints message that looks like an error but it is just infomational.
My original comment was that using ldd that way is meaningless, you are misusing ldd. You should only use ldd on executables. But getting that message may be useless, so it may be a bug.
>If __errno is specified in libc, why does ldd mention it?
Because libpthread isn't linked with libc?
Since mine doesn't get that message it may be a cosmetic bug after all.
082857.hqbrl02!?proc.17546.7.1: GP_CAT:1346: ERROR: pif: can't get address for EntryPoint '_ep_dl_instantiate' (impl 'registry.sl')
It seem you want to look for _ep_dl_instantiate?
>He tried it at his own HP-UX box and the error was not shown. His conclusion was that I had a "not-well-maintained" system.
I just now tried it and I don't get that message for your version of libpthread either. About the only differences are in the versions of ldd that you and admin have. What are they?
I have B.11.53, PHSS_33035. While installing this may fix ldd, I'm not sure it will fix your Tuxedo issue, but it can't hurt. At least find out what your admin has.
The latest dld patch is PHSS_35381.
>I do not really understand your answer about 'the command being illegal for me'.
Without a close look, it seems to me you are debugging something like:
$ echo "Unresolved symbol:"
It prints message that looks like an error but it is just infomational.
My original comment was that using ldd that way is meaningless, you are misusing ldd. You should only use ldd on executables. But getting that message may be useless, so it may be a bug.
>If __errno is specified in libc, why does ldd mention it?
Because libpthread isn't linked with libc?
Since mine doesn't get that message it may be a cosmetic bug after all.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP