HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Can't dlopen() a library containing Thread Local S...
Operating System - Linux
1830166
Members
5176
Online
109999
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
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
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
05-06-2007 12:28 AM
05-06-2007 12:28 AM
Can't dlopen() a library containing Thread Local Storage - Incorrect path beinh taken
I have built an executable that dlopens a shared lib. Both the exe and the lib are PARISC1.1.
The shared lib thats dlopen'ed by the exe is dependent on libjvm.sl. While building the shared lib, I have used -Wl,+s linker option and used java1.4 for linking i.e. something like -L/opt/java1.4/jre/lib/PA_RISC/server/ -ljvm.
However, when I am testing ans trying to run the exe on another machine that has java 1.5, I get an error saying that
Can't dlopen() a library containing Thread Local Storage: /opt/java1.4/jre/lib/PA_RISC/server//libjvm.sl
I am getting this even though I have set SHLIB_PATH to java1.5 paths and also set LD_PRELOAD to java1.5 libjvm.sl. Why is the SHLIB_PATH not being taken even when +s linker flag has been specified while building the shared lib?
Can someone help me out?
The shared lib thats dlopen'ed by the exe is dependent on libjvm.sl. While building the shared lib, I have used -Wl,+s linker option and used java1.4 for linking i.e. something like -L/opt/java1.4/jre/lib/PA_RISC/server/ -ljvm.
However, when I am testing ans trying to run the exe on another machine that has java 1.5, I get an error saying that
Can't dlopen() a library containing Thread Local Storage: /opt/java1.4/jre/lib/PA_RISC/server//libjvm.sl
I am getting this even though I have set SHLIB_PATH to java1.5 paths and also set LD_PRELOAD to java1.5 libjvm.sl. Why is the SHLIB_PATH not being taken even when +s linker flag has been specified while building the shared lib?
Can someone help me out?
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2007 03:48 PM
05-07-2007 03:48 PM
Re: Can't dlopen() a library containing Thread Local Storage - Incorrect path beinh taken
You seemed to have used the right options and ENV vars.
I suppose for your "other" machine, you could try to use the java1.4 libs to see if that works.
Otherwise try using ldd(1) to see why the variables aren't working:
export SHLIB_PATH=...
LD_PRELOAD=.../java1.5/.../libjvm.sl ldd your-shlib
See if there is more than one libjvm.sl?
Can you show us the chatr(1) output on your shlib?
I suppose you could also use tusc to see what libs are being opened during loading.
I suppose for your "other" machine, you could try to use the java1.4 libs to see if that works.
Otherwise try using ldd(1) to see why the variables aren't working:
export SHLIB_PATH=...
LD_PRELOAD=.../java1.5/.../libjvm.sl ldd your-shlib
See if there is more than one libjvm.sl?
Can you show us the chatr(1) output on your shlib?
I suppose you could also use tusc to see what libs are being opened during loading.
- Tags:
- tusc
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 2025 Hewlett Packard Enterprise Development LP