- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: unresolved symbols
Operating System - HP-UX
1753935
Members
9819
Online
108810
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
12-30-2004 04:35 AM
12-30-2004 04:35 AM
unresolved symbols
We are using aCC on an Itanium 11.23 system.
When we link with a number of OUR archive
libraries = no unresolved symbols.
Now, when link with same libraries, only
this time they are shared libaries. We
get a few unresolved symbols. These symbols
are references to our functions. Is has
nothing to do with system functions.
We can't figure out why there is this difference between using ONLY archive libraries
or ONLY shared libraries.
Any comments or suggestions would be
great.
Thank you.
Fred Bartholomai
When we link with a number of OUR archive
libraries = no unresolved symbols.
Now, when link with same libraries, only
this time they are shared libaries. We
get a few unresolved symbols. These symbols
are references to our functions. Is has
nothing to do with system functions.
We can't figure out why there is this difference between using ONLY archive libraries
or ONLY shared libraries.
Any comments or suggestions would be
great.
Thank you.
Fred Bartholomai
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2005 09:59 PM
01-03-2005 09:59 PM
Re: unresolved symbols
When you link with an archive library, all the addresses are resolved at link time. When you link with a shared library only data addresses are resolved at link time, library subroutines are linked at run time.
In 32-bit mode the dynamic loader is responsible for locating those shared libraries needed by an executable at run-time. The dynamic loader uses the attributes of the executable to help it determine where those shared libraries are located. The full path name may be used, or the environment variable SHLIB_PATH may be used (see chatr for more details).
It is possible that the dynamic loader is not loading the shared libraries you think it is loading and hence can't find certain symbols, or that there is another library with the same name, but earlier on its path. Without more details of your problem it is difficult to be more specific.
In 32-bit mode the dynamic loader is responsible for locating those shared libraries needed by an executable at run-time. The dynamic loader uses the attributes of the executable to help it determine where those shared libraries are located. The full path name may be used, or the environment variable SHLIB_PATH may be used (see chatr for more details).
It is possible that the dynamic loader is not loading the shared libraries you think it is loading and hence can't find certain symbols, or that there is another library with the same name, but earlier on its path. Without more details of your problem it is difficult to be more specific.
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