This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: libgomp.so CentOS - shared object cannot be dlopen()ed
- From: Brian Dessent <brian at dessent dot net>
- To: residentmoron <resident dot moron at gmail dot com>
- Cc: gcc-help at gcc dot gnu dot org
- Date: Fri, 07 Sep 2007 06:12:17 -0700
- Subject: Re: libgomp.so CentOS - shared object cannot be dlopen()ed
- References: <12538048.post@talk.nabble.com>
- Reply-to: gcc-help at gcc dot gnu dot org
residentmoron wrote:
> Here is the area of focus:
> libgomp.so.1: shared object cannot be dlopen()ed
>
> I am pretty sure that libgomp.so.1 is being resolved and actually
> found, however, I think this message means that the shared object
> cannot be dynamically opened. I have no idea how to move forward. I
> didn't think setting LD_LIBRARY_PATH would make a difference, however,
> I tried setting it anyway. I was right about that one. No
> difference.
>
> Do I need to recompile libgomp.so with some type of switches to make it
> dlopenable??
In 4.2.x libgomp was built with -Wl,-z,nodlopen to prevent it being
dlopened, I believe so that it could use a more efficient TLS model. I
think this has been changed in 4.3. See below:
<http://gcc.gnu.org/PR28482>
<http://gcc.gnu.org/ml/gcc-help/2007-04/threads.html#00300>
Brian