This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: libgomp and python: dlopen fails
- From: Andrew Haley <aph-gcc at littlepinkcloud dot COM>
- To: Sebastian Steiger <steigers at phys dot ethz dot ch>
- Cc: gcc-help at gcc dot gnu dot org
- Date: Wed, 25 Apr 2007 16:06:02 +0100
- Subject: Re: libgomp and python: dlopen fails
- References: <462F6C16.3030808@phys.ethz.ch>
Sebastian Steiger writes:
> I'd like to post again the question Iordan Hristov had a couple of
> months ago (http://gcc.gnu.org/ml/gcc-help/2006-09/msg00164.html), but
> no answer was given back then.
>
> I am using a C++ shared library as a module to import in python
> (wrapping my functions into the python API is done by SWIG). This
> library depends on libgomp.so. I tried with the gomp version shipped
> with RHEL4 gcc-4.1 and with a version compiled by myself from source
> (April 2007) on a 64bit Red Hat Linux machine. I get the following error:
>
>
> ImportError: libgomp.so.1: shared object cannot be dlopen()ed
>
>
> I have more libraries on which the imported library depends, but they
> all work. libgomp also works when I use it in a normal c++ program.
>
> Does anybody have an idea what to do? I must admit that I'm not familiar
> with dlopen(). I initially thought that the problem had something to do
> with the library being stripped or "nm" not giving me any objects, but
> the version compiled by myself didn't have that.
>
> I think that libgomp should be capable of being imported into python,
> just as the AMD core math library is.
What does ldd say about your python library?
What does 'file' say about your library and about libgomp.so.1?
Setting LD_DEBUG=files may help
We need to see that before progressing.
Andrew.