From: David Edelsohn <dje.gcc@gmail.com>
To: Michael Haubenwallner <michael.haubenwallner@salomon.at>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, regression?] Support --static-libstdc++ with native AIX ld
Date: Mon, 28 Jan 2013 15:07:00 -0000 [thread overview]
Message-ID: <CAGWvny=gzeHUcrbtBezL6K0jZ5fX420JxCVzCGrebnwvWonNTA@mail.gmail.com> (raw)
In-Reply-To: <51063FCD.7010802@salomon.at>
On Mon, Jan 28, 2013 at 4:07 AM, Michael Haubenwallner
<michael.haubenwallner@salomon.at> wrote:
> But still curious if you've been able to reproduce the problem,
> and why you didn't encounter this problem beforehand.
As I mentioned before, because of --boot-ld-flags, with earlier libgcc
and libstdc++ installed in that directory.
> Yes, but (you've asked) here is this situation I don't want to configure extra deplib-prefixes
> for (remember bullfreeware is listed as provider for gcc-binaries):
>
> * bullfreeware's libiconv-1.13.1 and gettext-0.17 is installed in /opt/freeware,
> * /usr/lib/libintl.a is symlinked to /opt/freeware/lib (by bullfreeware's RPM),
> * /usr/lib/libiconv.a is the original AIX' one.
>
> Now, /usr/lib/libintl.a needs /opt/freeware/lib/libiconv.a[libiconv.so.2], and it does
> contain the correct RUNPATH. But subsequent binaries linking against /usr/lib/libintl.a
> don't (necessarily) know about the need to add /opt/freeware/lib as RUNPATH, so these
> binaries break with libiconv.so.2 not being found as member of /usr/lib/libiconv.a, because
> AIX unfortunately does stop its shared-library search at the first archive filename found.
>
> This also is the main reason for my filename-based-shared-library-versioning thing.
Over the weekend, I successfully tested a different way to configure
and build: all static libraries. If you build and privately install
GMP, MPFR, MPC and LIBICONV configured as static libraries
(--enable-static --disable-shared) and install in /prereq, then,
combined with your patch to enable --static-libstdc++ --static-libgcc,
the resulting GCC only depends on AIX libc.a -- no other shared
libraries. Bull Freeware can distribute the shared versions of the
libraries for other applications, but they do not need to be GCC
dependencies.
- David
next prev parent reply other threads:[~2013-01-28 15:07 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 [this message]
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
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='CAGWvny=gzeHUcrbtBezL6K0jZ5fX420JxCVzCGrebnwvWonNTA@mail.gmail.com' \
--to=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=michael.haubenwallner@salomon.at \
/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).