public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/52623] 4.7.0-RC-20120314: bootstrap failure on AIX due to multilib and using C++ in post-stage1
Date: Fri, 23 Mar 2012 00:03:00 -0000	[thread overview]
Message-ID: <bug-52623-4-nBRgILGxEE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52623-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52623

--- Comment #10 from David Edelsohn <dje at gcc dot gnu.org> 2012-03-22 23:53:14 UTC ---
I recognize that a lot of FLOSS packages are developed on x86/Linux, but
POWER/AIX is not x86/Linux.  Upon further consideration, I am concerned that
your proposal forces all applications to link using -brtl.  Your proposal
implies that libtool and GCC should build all shared libraries using your
SVR4-compatibility design.  One could adjust GCC and libtool to link all
applications with -brtl, but libraries built the current way can work with
older releases of GCC and with XLC.  Even with the GCC change, many users will
be confused by XLC breakage and it will be a steep learning curve to teach
users to add -brtl to all applications that use newly-built FLOSS libraries
using the new libtool design.

I agree that AIX is gratuitously different from SVR4/Solaris/Linux with no
particular benefit.  However, it is what it is.  Without cooperation from IBM
and AIX to convert it to SVR4-compatibility by default, I'm not convinced that
imposing this compatibility is a good idea when the GNU tools do not control
the entire system stack.

An additional problem is Binutils "strip" command does not support the -e/-E
command line option to set F_LOADONLY.


  parent reply	other threads:[~2012-03-22 23:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19 17:20 [Bug bootstrap/52623] New: " michael.haubenwallner at salomon dot at
2012-03-19 17:25 ` [Bug bootstrap/52623] " michael.haubenwallner at salomon dot at
2012-03-20 14:16 ` dje at gcc dot gnu.org
2012-03-21  9:44 ` michael.haubenwallner at salomon dot at
2012-03-21 14:44 ` michael.haubenwallner at salomon dot at
2012-03-22  5:55 ` dje at gcc dot gnu.org
2012-03-22  9:43 ` michael.haubenwallner at salomon dot at
2012-03-22 19:26 ` dje at gcc dot gnu.org
2012-03-22 20:43 ` michael.haubenwallner at salomon dot at
2012-03-22 21:40 ` dje at gcc dot gnu.org
2012-03-23  0:03 ` dje at gcc dot gnu.org [this message]
2012-03-23 10:22 ` michael.haubenwallner at salomon dot at
2012-03-23 10:43 ` michael.haubenwallner at salomon dot at
2012-03-23 16:45 ` michael.haubenwallner at salomon dot at
2012-03-27 16:49 ` dje at gcc dot gnu.org
2012-03-28  8:32 ` michael.haubenwallner at salomon dot at
2012-03-28 13:00 ` dje at gcc dot gnu.org
2012-03-28 14:25 ` michael.haubenwallner at salomon dot at
2013-01-30 16:53 ` dje at gcc dot gnu.org
2015-02-06 16:01 ` dje at gcc dot gnu.org

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=bug-52623-4-nBRgILGxEE@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).