From: David Edelsohn <dje.gcc@gmail.com>
To: Mike Stump <mrs@mrs.kithrup.com>
Cc: Michael Haubenwallner <michael.haubenwallner@salomon.at>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, regression?] Support --static-libstdc++ with native AIX ld
Date: Mon, 28 Jan 2013 21:42:00 -0000 [thread overview]
Message-ID: <CAGWvny=aMtM5iziXOrTArFAbmJRzouFJ6qFfnQ+YjGaLTC0Bcw@mail.gmail.com> (raw)
In-Reply-To: <6F86C30B-99B2-4338-95E1-F67476F0D758@mrs.kithrup.com>
On Mon, Jan 28, 2013 at 4:17 PM, Mike Stump <mrs@mrs.kithrup.com> wrote:
> On Jan 28, 2013, at 7:07 AM, David Edelsohn <dje.gcc@gmail.com> wrote:
>> Over the weekend, I successfully tested a different way to configure
>> and build: all static libraries.
>
> Yeah, I think our build instructions for the dependent libraries should say to build them statically.
A number of GCC developers who already do this.
I previously had problem on AIX with an earlier release of GCC that
was built with Graphite because one of the dependent libraries used
C++, but GCC was not linked with libstdc++ at the time. The only way
to break the C++ dependency of the library separate from GCC was
through shared libraries.
If one can link GCC against static libraries, it definitely simplifies
things and avoids potential conflicts with multiple versions of GCC
installed.
- David
next prev parent reply other threads:[~2013-01-28 21:42 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 [this message]
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=aMtM5iziXOrTArFAbmJRzouFJ6qFfnQ+YjGaLTC0Bcw@mail.gmail.com' \
--to=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=michael.haubenwallner@salomon.at \
--cc=mrs@mrs.kithrup.com \
/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).