- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- HPUX-pa libCsup.2 problem
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
Discussions
Discussions
Forums
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
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
тАО09-21-2006 02:25 PM
тАО09-21-2006 02:25 PM
HPUX-pa libCsup.2 problem
I HPUX-pa software developer with NCR. Currently we are having an issue with unresolved symbol in our 64bit library during run time. The unresolved symbol is __ShlTerm. The truss ouput shows that
/usr/lib/pa20_64/libCsup.2 is opened and mapped, and nm shows that __shlTerm is defined there.
Then these facts are true, what could be other factors causing __shlTerm not resolved?
Thanks.
fs185009@ncr.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-25-2006 12:01 PM - edited тАО10-29-2011 01:55 AM
тАО09-25-2006 12:01 PM - edited тАО10-29-2011 01:55 AM
Re: HP-UX PA libCsup.2 problem
__shlTerm (not __ShlTerm) is exported from libCsup.2 so you should not be getting this unsat, provided you include libCsup.2 on your link line. Were there any other errors?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-25-2006 12:10 PM
тАО09-25-2006 12:10 PM
Re: HPUX-pa libCsup.2 problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-25-2006 12:55 PM - edited тАО10-29-2011 01:56 AM
тАО09-25-2006 12:55 PM - edited тАО10-29-2011 01:56 AM
Re: HP-UX PA libCsup.2 problem
>the library built by aC++, there is no need to supply -lCsup.
This is only correct if you have a aC++ executable.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-25-2006 01:27 PM
тАО09-25-2006 01:27 PM
Re: HPUX-pa libCsup.2 problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-25-2006 01:43 PM - edited тАО10-29-2011 01:56 AM
тАО09-25-2006 01:43 PM - edited тАО10-29-2011 01:56 AM
Re: HP-UX PA libCsup.2 problem
>the linking was ok, because library did get built.
Since you don't usually get unsat errors when building shlibs, this is meaningless.
Can you explain when you are getting the error? At load or runtime? The latter means shl_load or dlopen.
And what do the errors look like? And what linker patch do you have?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-25-2006 02:48 PM
тАО09-25-2006 02:48 PM
Re: HPUX-pa libCsup.2 problem
dlopen failed: Unsatisfied data symbol '__shlTerm' in load module A
- Tags:
- dlopen
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-25-2006 03:10 PM - edited тАО10-29-2011 01:57 AM
тАО09-25-2006 03:10 PM - edited тАО10-29-2011 01:57 AM
Re: HP-UX PA libCsup.2 problem
>when dlopen library A which uses the __shlTerm, dlopen failed
Now you need to answer the question implied by: This is only correct if you have a aC++ executable.
And what are your dlopen parms?
If this is a C executable, you need to follow the directions on:
http://www.docs.hp.com/en/7762/5991-4874/distributing.htm#linking
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-26-2006 05:56 AM
тАО09-26-2006 05:56 AM
Re: HPUX-pa libCsup.2 problem
Did you mean if there is aC++ executables on the system that builds the library or the runtime system?
The build system does have aCC executables and we use aCC to do the linking.
For the runtime system, I dont know if there is a aCC or aC++.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-26-2006 11:29 AM - edited тАО10-29-2011 01:58 AM
тАО09-26-2006 11:29 AM - edited тАО10-29-2011 01:58 AM
Re: HP-UX PA libCsup.2 problem
>Did you mean if there is aC++ executables
No. I meant what type of application is doing the dlopen. Is it C or aC++?
(Also, what linker patch do you have installed?)