topic Re: Cannot dlopen load module '/usr/lib/pa20_64/libpthread.1' because it contains thread specific data. in Operating System - HP-UX

Cannot dlopen load module '/usr/lib/pa20_64/libpthread.1' because it contains thread specific data.

Rock Brown — Thu, 03 Mar 2005 17:07:05 GMT

I have an 64-bit executable built without thread support, trying to load a shared library
linked with -lpthread and are unable to
load the library. I was looking for solution
that allows the two to co-exist versus,
removing threading from my library or adding
to existing executable.

Any help is appreciated.

Thanks,

Rock

Re: Cannot dlopen load module '/usr/lib/pa20_64/libpthread.1' because it contains thread specific data.

MAUCCI_2 — Fri, 04 Mar 2005 08:19:57 GMT

Have you tried relinking your application with -lpthread?

++Cyrille

Re: Cannot dlopen load module '/usr/lib/pa20_64/libpthread.1' because it contains thread specific data.

Alexey Roytman — Sun, 06 Mar 2005 04:03:54 GMT

If you really-really do not want to relink either of them, you can try to define environment variable LD_PRELOAD to be /usr/lib/pa20_64/libpthread.1 before starting the application:
LD_PREALOAD=/usr/lib/pa20_64/libpthread.1
export LD_PRELOAD
exec your_application_binary

Re: Cannot dlopen load module '/usr/lib/pa20_64/libpthread.1' because it contains thread specific data.

Rock Brown — Mon, 07 Mar 2005 17:30:07 GMT

Thanks for the feedback.

I went with linking against -lpthread for
various reasons and it fixed the problem, however I then tried to dlopen() a 2nd shared library from within the first loaded
shared library and the problem returned.
The 2nd failure was resolved by linking
my executable against -lcl, which is
used by the last shared library. The
last shared library is not mind so I
can't change it. I still prefer a solution
I could implement in the first shared library since that is my development focus.

Re: Cannot dlopen load module '/usr/lib/pa20_64/libpthread.1' because it contains thread specific data.

Alexey Roytman — Tue, 08 Mar 2005 03:22:23 GMT

Either relink both executable and first library with -lpthread and with -lcl, or set LD_PRELOAD to have both libpthread and libcl (full pathes, colon-separated).