Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 1880 - bootstrap attempt with gcc 3 fails - possible gcc3.0.4-r3.ebuild bug?
Summary: bootstrap attempt with gcc 3 fails - possible gcc3.0.4-r3.ebuild bug?
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Unspecified (show other bugs)
Hardware: x86 Linux
: High blocker (vote)
Assignee: Daniel Robbins (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-04-17 13:05 UTC by Julian Urquijo
Modified: 2003-02-04 19:42 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Julian Urquijo 2002-04-17 13:05:22 UTC
I was attempting to follow the instructions in the "Gcc 3.0.4 installed
system" post to gentoo-dev and ran into a problem.

These are the steps I followed:

Normal stage1 install, followed by emerge rsync.

rm /etc/make.profile & ln -s /usr/portage/profiles/default-1.0-gcc3
/etc/make.profile

edit make.conf

scripts/bootstrap.sh

It starts building binutils, etc. then fails during the GCC 3 compile with
the following errors:

Bootstrapping the compiler
make [1]: Entering directory '/var/tmp/portage/gcc3.0.4-r3/work/build/gcc'
(cd /var/tmp/portage/gcc3.0.4-r3/work/gcc-3.0.4 /gcc && autoconf)
/bin/sh: autoconf : command not found
make [1] *** [/var/tmp/portage/gcc3.0.4-r3/work/build/gcc/configure] Error
127
make [1] : Leaving directory /var/tmp/portage/gcc3.0.4-r3/work/build/gcc
make: *** [bootstrap-lean] Error 2

!!! Error: The ebuild did not complete successfully
!!! Function src_compile, Line 79, Exitcode 2
!!! (no error message)
!!! emerge aborting on /usr/portage/sys-devel/gcc/gcc-3.0.4-r3.ebuild
Comment 1 Daniel Robbins (RETIRED) gentoo-dev 2002-04-21 17:04:16 UTC
gcc3 needs autoconf in the stage1 image.
Comment 2 Martin Blix Grydeland 2002-04-22 14:37:49 UTC
It seems this is caused by the name transformation patch copied from Mandrake.
This causes the build process to try to rebuild the makefiles because
Makefile.in has been changed, thus needing autoconf.

As far as I know the Mandrake patch only takes effect when building a cross
compiler, or a compiler with special binary names (e.g. gcc-3.0). In the
bootstrap process this seems to me to be a non-issue. One solution might
therefor be (to add autoconf as a dependancy and include the Mandrake patch)
only if the 'build' use var is not set.

Best regards
Martin Blix Grydeland
Comment 3 Martin Schlemmer (RETIRED) gentoo-dev 2002-04-25 15:18:27 UTC
Ok, try -r4 in a while.
Comment 4 Brandon Low (RETIRED) gentoo-dev 2002-04-26 16:30:07 UTC
the mandrake patch is also buggy, if  in developer mode "noclean" is on you can 
end up with double mangled names which is really funky.  
Comment 5 Julian Urquijo 2002-04-29 09:27:46 UTC
gcc-3.0.4-r4 works!

I've successfully installed a gcc 3 bootstrapped system.

Not sure if this was the "right" way to do it, but I bootstrapped twice. 1st 
time through the gcc from the boot image doesn't accept the -march athlon flag 
(so i bootstrapped with the -i686 flag in make.conf). After the 1st bootstrap, 
I edited make.conf, changing the -march i686 flag to athlon and ran the 
bootstrap script again.