From: "Jonathan Saxton" <jsaxton@appsecinc.com>
To: <gcc-help@gcc.gnu.org>
Cc: "'Ben Scurr'" <bs@teamwpc.co.uk>
Subject: RE: AIX 5.3 gcc 4.1.2 bootstrap error
Date: Tue, 18 Mar 2008 16:44:00 -0000 [thread overview]
Message-ID: <000501c88917$3d881240$381110ac@nycapt35k.com> (raw)
In-Reply-To: <47DFD46E.9E699E4D@dessent.net>
Brian:
Yes I knew about that and I had been careful to supply the appropriate
"--with" options to the configure script. What I didn't know was how
aggressive the stage 3 configuration was in searching for the gnu tools. I
only discovered the problem because I just happened to be watching the
screen at the moment stage 3 started. Of course everything scrolled off too
quickly for me to read but a repeat of the build piped through tee showed
"Target ld ..." and "Target as ..." to be something other than the native
AIX tools. I purged all traces of binutils and everything worked.
Subsequently I did restore cxxfilt because that is useful and harmless but I
think a warning should be added to the text which you mentioned.
-----Original Message-----
From: gcc-help-owner@gcc.gnu.org [mailto:gcc-help-owner@gcc.gnu.org] On
Behalf Of Brian Dessent
Sent: 18 March, 2008 10:41
To: Jonathan Saxton
Cc: 'Ben Scurr'; gcc-help@gcc.gnu.org
Subject: Re: AIX 5.3 gcc 4.1.2 bootstrap error
Jonathan Saxton wrote:
>
> I had lots of difficulty building 4.2.2 on AIX 5.2. Problem turned out to
> be binutils. I found that I had to delete binutils altogether. It was
not
> sufficient to use the make options to specify the native versions of ld
and
For what it's worth gcc documents this requirement:
<http://gcc.gnu.org/install/specific.html#x-ibm-aix>
quote:
> The native as and ld are recommended for bootstrapping on AIX 4 and
> required for bootstrapping on AIX 5L. The GNU Assembler reports that it
> supports WEAK symbols on AIX 4, which causes GCC to try to utilize weak
> symbol functionality although it is not supported. The GNU Assembler and
> Linker do not support AIX 5L sufficiently to bootstrap GCC. The native
> AIX tools do interoperate with GCC.
Brian
prev parent reply other threads:[~2008-03-18 16:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 12:43 Ben Scurr
2008-02-14 13:44 ` Ralf Wildenhues
2008-02-19 17:03 ` Thomas Mittelstaedt
2008-03-18 14:15 ` Jonathan Saxton
2008-03-18 14:41 ` Brian Dessent
2008-03-18 16:44 ` Jonathan Saxton [this message]
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='000501c88917$3d881240$381110ac@nycapt35k.com' \
--to=jsaxton@appsecinc.com \
--cc=bs@teamwpc.co.uk \
--cc=gcc-help@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).