This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/24119] gcc-4.x fails to build on AIX 5.2.0.0-ML04
- From: "h dot m dot brand at xs4all dot nl" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 6 Oct 2005 08:44:27 -0000
- Subject: [Bug target/24119] gcc-4.x fails to build on AIX 5.2.0.0-ML04
- References: <bug-24119-11434@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #12 from h dot m dot brand at xs4all dot nl 2005-10-06 08:44 -------
Subject: Re: gcc-4.x fails to build on AIX 5.2.0.0-ML04
On 6 Oct 2005 06:33:16 -0000, "h dot m dot brand at xs4all dot nl"
<gcc-bugzilla@gcc.gnu.org> wrote:
> ------- Comment #11 from h dot m dot brand at xs4all dot nl 2005-10-06
> 06:33 ------- Subject: Re: gcc-4.x fails to build on AIX 5.2.0.0-ML04
>
> On 6 Oct 2005 04:30:37 -0000, "dje at gcc dot gnu dot org"
> <gcc-bugzilla@gcc.gnu.org> wrote:
>
> > ------- Comment #10 from dje at gcc dot gnu dot org 2005-10-06 04:30
> > ------- You say: "I re-ran without -B", but the Make output clearly shows
> > the command still present:
> >
> > CC_FOR_BUILD=" stage1/xgcc -Bstage1/
> > -B/usr/local/ppc64/powerpc-ibm-aix5.2.0.0/bin/"
> >
> > The configuration process remembers the option. You need to completely
> > delete the configure directory, reconfigure, and rebuild. With the extra
> > -B present, you are not using the correct compiler for the stage2
> > bootstrap with stage1 compiler. It appears that your problems continue
> > to be cockpit error.
>
> That's what I always do. 'rm -rf obj' before I reconfigure
>
> I'll move the /usr/local/ppc64 completely out of the way, so it won't be
> able to find it. That of course makes building with gcc-4.0.0 quite a bit
> harder, but I'll try
That worked. But I still saw the -B added to all the lines, but now that that
folder is not there, all goes smooth
Here's the script I used to build:
--8<---
#!/usr/bin/sh
export CONFIG_SITE=
export CCFLAGS=-Wl,-bbigtoc
export PATH=.:/data/gcc-402/bin:/pro/local/bin
export PATH=$PATH"":/usr/vac/bin:/usr/bin:/usr/ccs/bin
export PATH=$PATH"":/usr/bin/X11R6:/usr/bin/X11
rm -rf obj
mkdir obj
cd obj
../src/configure \
--enable-languages=c \
--prefix=/usr/local/ppc64 --with-local-prefix=/usr/local/ppc64 \
--disable-shared \
--disable-nls
make bootstrap-lean
-->8---
/data/gcc-402 is the gcc I got from someone else, and the /usr/local/ppc64
that is used to install it in was temporary moved to out of sight.
As you can see: *I* did not put any -B options in there, so it must either be
the Makefiles or configure that puts them in because of my --prefix and/or
--with-local-prefix
Note: for AIX moving the target folder out of the way is not such a big deal,
since I do not use binutils on AIX, and my GNU make is installed in a public
bin, but this behaviour might not be very helpful on OS's that require
binutils to create gcc (/me thinks HP-UX 11.i/64)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24119