From: Michael Haubenwallner <michael.haubenwallner@salomon.at>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, regression?] Support --static-libstdc++ with native AIX ld
Date: Wed, 30 Jan 2013 15:55:00 -0000 [thread overview]
Message-ID: <51093FD7.9090006@salomon.at> (raw)
In-Reply-To: <CAGWvny=5LROGHoj-AJJfsEJbcJdtTLEE_9Xa1ZtromTy5Y27Cg@mail.gmail.com>
On 01/30/2013 03:16 PM, David Edelsohn wrote:
> <michael.haubenwallner@salomon.at> wrote:
>> 4: Also, LD_LIBRARY_PATH points to ppc64/libstdc++-v3/.libs/ while using
>> 32bit gcc/xgcc to build libatomic.a.
>> => This is the one that /does/ break, as that 64bit libstdc++.a is there now.
> Originally, I was using --boot-ld-flags which included /usr/gnu/lib
> first in the path, so an older version of libstdc++ was found.
Yes, but - sorry for being nit-picky - could you find out if your
/usr/gnu/lib/libstdc++.a was a static-only archive?
> Now, after your patch, cc1plus is statically linked with libstdc++.a.
Yes, although the problem was with xgcc already (before cc1plus is executed).
/haubi/
next prev parent reply other threads:[~2013-01-30 15:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 19:55 David Edelsohn
2013-01-24 9:18 ` Michael Haubenwallner
2013-01-24 17:45 ` David Edelsohn
2013-01-25 13:56 ` Michael Haubenwallner
2013-01-25 15:56 ` David Edelsohn
2013-01-27 2:16 ` David Edelsohn
2013-01-28 9:08 ` Michael Haubenwallner
2013-01-28 15:07 ` David Edelsohn
2013-01-28 21:17 ` Mike Stump
2013-01-28 21:42 ` David Edelsohn
2013-01-30 11:35 ` Michael Haubenwallner
2013-01-30 14:16 ` David Edelsohn
2013-01-30 15:55 ` Michael Haubenwallner [this message]
2013-01-30 16:02 ` David Edelsohn
2013-01-30 16:07 ` Michael Haubenwallner
2013-01-30 16:35 ` David Edelsohn
2013-01-24 21:59 ` David Edelsohn
-- strict thread matches above, loose matches on Subject: below --
2013-01-23 11:24 Michael Haubenwallner
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=51093FD7.9090006@salomon.at \
--to=michael.haubenwallner@salomon.at \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@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).