From: Perry Smith <pedzsan@gmail.com>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: AIX library issues
Date: Mon, 24 Oct 2011 00:59:00 -0000 [thread overview]
Message-ID: <25EA9ADB-AC03-42B9-9090-545D5FC9ADC7@gmail.com> (raw)
In-Reply-To: <CAGWvnyng21Dq5MVWLP4cTvn0=wZvFQEz8c+ATKRfv_679OYr3A@mail.gmail.com>
On Oct 18, 2011, at 9:59 AM, David Edelsohn wrote:
> On Mon, Oct 17, 2011 at 10:05 PM, Perry Smith <pedzsan@gmail.com> 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
pedz
next prev parent reply other threads:[~2011-10-23 14:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 4:48 Perry Smith
2011-10-18 8:30 ` Jonathan Wakely
2011-10-18 10:28 ` Jonathan Wakely
2011-10-18 15:37 ` David Edelsohn
2011-10-24 0:59 ` Perry Smith [this message]
2011-10-24 2:36 ` David Edelsohn
2011-10-24 9:45 ` Perry Smith
[not found] ` <5FB999D3-E0FA-4AC7-A26A-DAA4397D833F@gmail.com>
2011-10-25 6:31 ` David Edelsohn
2011-10-25 9:13 ` Richard Guenther
2011-10-25 9:24 ` Arnaud Charlet
2011-10-25 15:14 ` David Edelsohn
2011-10-25 16:05 ` Arnaud Charlet
2011-11-08 18:44 ` David Edelsohn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=25EA9ADB-AC03-42B9-9090-545D5FC9ADC7@gmail.com \
--to=pedzsan@gmail.com \
--cc=dje.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).