This is the mail archive of the
mailing list for the GCC project.
Re: AIX library issues
On Oct 18, 2011, at 9:59 AM, David Edelsohn wrote:
> On Mon, Oct 17, 2011 at 10:05 PM, Perry Smith <firstname.lastname@example.org> wrote:
>> dump -H libstdc++.so.6
>> /usr/work/src/gcc-4.5.2/configure --prefix=/gsa/ausgsa/projects/r/ruby --with-gmp=/gsa/ausgsa/projects/r/ruby --with-mpfr=/gsa/ausgsa/projects/r/ruby --with-mpc=/gsa/ausgsa/projects/r/ruby --disable-nls --enable-threads=aix --with-libiconv-prefix=/usr --enable-languages=c,c++
> AIX inserts the list of libraries provided with -L options on the link
> command line into the default search path. If you want, you can edit
> libtool created for libstdc++ to add
> -Wl,-blibpath:/gsa/ausgsa/projects/r/ruby/lib:/usr/lib:/lib and relink
> libstdc++ (or edit the path in the shared object header directly).
I'm working on a real solution to this but bumped into a question:
libgomp.so.1 wants libc.a, libpthreads.a, and libgcc_s.a. The first two do not present a problem. But there are four libgcc_s.a (normal, ppc64, pthread, and ppc64+pthread).
Note that there is also four versions of libgomp.so.1 (normal, ppc64, pthread, ppc64+pthread).
My question is: which libgcc_s.a should I link to? (this question is for each of the four versions of libgomp.so.1).
Setting LIBPATH or whatever I do is going to override the internal path (since the internal path is broken). So, this may be a question that has never been asked or answered.
My knee jerk is that the normal libgomp.so.1 wants the normal libgcc_s.a, the ppc64 wants the ppc64, etc. But I notice that it will always include pthread so that is what caused me to pause and ask.
Part of me wonders if the two non-pthread versions of libgomp make any sense. I don't really know anything about libgomp.
Thank you for your time