- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- shl_load unresolved linking with archive libraries
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
05-29-2002 05:25 AM
05-29-2002 05:25 AM
shl_load unresolved linking with archive libraries
/usr/ccs/bin/ld: Unsatisfied symbols:
shl_load (code)
shl_unload (code)
shl_findsym (code)
Are these the correct compiler flags for HP-UX 11.11, PA1.X, HP-C? (I'd like to avoid linking with libdld.sl!)
Thanks,
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-29-2002 06:31 AM
05-29-2002 06:31 AM
Re: shl_load unresolved linking with archive libraries
Thjese are coming from dld.sl for DNSS and you have no choice I am afraid
Steve steel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-31-2002 05:42 AM
05-31-2002 05:42 AM
Re: shl_load unresolved linking with archive libraries
Thanks for the reply. I'm unclear on DNSS, is that Domain Name Service? A function like gethostbyname would only be in libc.sl and not libc.a? Is this a feature, or a bug?
Thanks,
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-31-2002 05:59 AM
05-31-2002 05:59 AM
Re: shl_load unresolved linking with archive libraries
Hi,
This has nothing to do with gethostbyname etc
The libdld.sl is used by loader when
you start a program to link in shared
libs your program uses.
Check if your program has calls to shl_load
etc. If not, I guess you have trivial
error in your compiler/linker command.
To minimize uncertain factors you could start
with dropping the -Wl,-a archive option
to the compiler.
Regards
Olav
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-31-2002 11:45 AM
05-31-2002 11:45 AM
Re: shl_load unresolved linking with archive libraries
I think Steve is correct, the resolver routines reference shl_load, etc.
/usr/ccs/bin/ld: Unsatisfied symbols:
shl_load (first referenced in /usr/lib/libc.a(gethostent.o)) (code)
shl_findsym (first referenced in /usr/lib/libc.a(gethostent.o)) (code)
A sample program is listed in the man page for gethostent. I can't compile this without shared libraries.
I'm trying to compile NTP so it will run on HP-UX 10.X and 11.X. It was suggested that I build it without shared libraries, hence my current predicament.
Thanks,
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-11-2002 04:05 AM
06-11-2002 04:05 AM
Re: shl_load unresolved linking with archive libraries
WARNINGS
Programs that use the interfaces described in this manpage cannot be
linked statically because the implementations of these functions
employ dynamic loading and linking of shared objects at run time.