- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- what hpux c functions require linking to a shared ...
Operating System - Linux
1753886
Members
7177
Online
108809
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
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
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
07-25-2002 08:09 AM
07-25-2002 08:09 AM
what hpux c functions require linking to a shared lib?
Hi,
I've encountered a problem porting some code to HPUX. When linking
one of the executables, I get unresolved symbols shl_load, shl_unload
and shl_findsym. I found out on this forum that there are some
hpux calls that require you to link to a shared library (like
gethostbyname for instance), and that there's no way around it.
My program is supposed to run early at boot time, and I don't want to
depend on shared libs being around (I am using the '-Wl,-a archive'
option when linking).
I'm not using gethostbyname - but I guess there are other functions
on hpux that have the same requirement. I'd like to know what are they,
so that I can try to work around it.
Is there a list of those somewhere? Or how can I go about finding that
out?
Thanks,
Iva
I've encountered a problem porting some code to HPUX. When linking
one of the executables, I get unresolved symbols shl_load, shl_unload
and shl_findsym. I found out on this forum that there are some
hpux calls that require you to link to a shared library (like
gethostbyname for instance), and that there's no way around it.
My program is supposed to run early at boot time, and I don't want to
depend on shared libs being around (I am using the '-Wl,-a archive'
option when linking).
I'm not using gethostbyname - but I guess there are other functions
on hpux that have the same requirement. I'd like to know what are they,
so that I can try to work around it.
Is there a list of those somewhere? Or how can I go about finding that
out?
Thanks,
Iva
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-09-2006 02:49 PM
03-09-2006 02:49 PM
Re: what hpux c functions require linking to a shared lib?
On IPF, libc is only shared.
On PA, there is usually a warning on the man page:
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.
Of course you could use nm -px libc.a and scan the unsats.
On PA, there is usually a warning on the man page:
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.
Of course you could use nm -px libc.a and scan the unsats.
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP