GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Problems with shared libraries
Operating System - HP-UX
1848164
Members
5342
Online
104022
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
Forums
Discussions
back
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
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
09-08-2009 01:36 AM
09-08-2009 01:36 AM
Problems with shared libraries
Hello!
I have a problem with shared dynamic libraries in HP-UX:
After compiling and linking, when I do an ldd over the executable file, it refers to libraries with absolute paths, so i find problems to execute the program in other machines, because the path does no exist.
A piece of the ldd result is:
/usr/lib/libdld.2 => /usr/lib/libdld.2
As you can see, the libraries refer to absolute paths, instead of relative paths:
./libdld.2 -> usr/lib/libdld.2
Any ideas about the problem??
Thank you in advance
I have a problem with shared dynamic libraries in HP-UX:
After compiling and linking, when I do an ldd over the executable file, it refers to libraries with absolute paths, so i find problems to execute the program in other machines, because the path does no exist.
A piece of the ldd result is:
/usr/lib/libdld.2 => /usr/lib/libdld.2
As you can see, the libraries refer to absolute paths, instead of relative paths:
./libdld.2 -> usr/lib/libdld.2
Any ideas about the problem??
Thank you in advance
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-08-2009 03:11 AM
09-08-2009 03:11 AM
Re: Problems with shared libraries
>it refers to libraries with absolute paths
This is an illusion. If you have enabled embedded (ld's +b) or SHLIB_PATH (ld's +s), you can use those paths on other machines.
>A piece of the ldd result is:
/usr/lib/libdld.2 => /usr/lib/libdld.2
It is illegal to use this as an example since libdld is always there and can't be moved. Your example should include YOUR shlibs.
This is an illusion. If you have enabled embedded (ld's +b) or SHLIB_PATH (ld's +s), you can use those paths on other machines.
>A piece of the ldd result is:
/usr/lib/libdld.2 => /usr/lib/libdld.2
It is illegal to use this as an example since libdld is always there and can't be moved. Your example should include YOUR shlibs.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-08-2009 03:23 AM
09-08-2009 03:23 AM
Re: Problems with shared libraries
You can also have paths with $ORIGIN.
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 2026 Hewlett Packard Enterprise Development LP