Bug 8130 – GCC 3.2 ebuild fails with error message about xgcc

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description Pardsbane 2002-09-19 19:49:59 UTC]

Hello, I am trying to upgrade from 1.2 to 1.4rc1. The update-step1 and update-
step2 scripts worked fine, but update-step3 fails with errors. I examined the 
update scripted and figured out that it was running:

ebuild -e gcc blah blah...

Since I knew that it had gotten to the gcc part of that ebuild ok, but was 
failing on gcc, I just did this:

ebuild gcc

and got the same errors.

While trying to build libsupc++, and specifically del_op.c (to del_op.lo), I 
get this error message:

xgcc: cannot specify -o with -c or -S and multiple compilations

And the ebuild stops. Currently I have an unbootable system because of this. :(

[Comment 1 Pardsbane 2002-09-20 10:09:20 UTC]

Oops, turns out this is 1/2 user error, 1/2 documentation bug. This URL:  http://www.freehackers.org/gentoo/gccflags/flag_gcc3opt.html  referred to via this URL:  http://www.gentoo.org/doc/upgrade-to-gentoo-1.4.html  Instructs users to do the following (for example):   CFLAGS="-march=pentium3 -O3 -pipe -fomit-frame-pointer    -fforce-addr -falign-functions=4 -fprefetch-loop-arrays" CXXFLAGS=CFLAGS  However, typing "echo CXXFLAGS" results in: What now? echo $CXXFLAGS CFLAGS  The correct solution is: CXXFLAGS="${CFLAGS}"  which works.  Anyway, if I had been paying attention, I would have caught that, but its still a documentation bug, and while its not on the official Gentoo website, it IS linked to by the official gentoo 1.2 to 1.4 upgrade documentation. 

[Comment 2 Pardsbane 2002-09-20 10:14:05 UTC]

Sorry about the formatting of the previous comment, looks like Konq 
+ bugzilla doesn't peserve hard returns. Anyway, the above comment 
refers to the variables defined in /etc/make.conf of course. 

[Comment 3 Nicholas Jones (RETIRED) 2002-09-22 19:43:26 UTC]

See additional comment #1

[Comment 4 Thomas Capricelli 2002-09-23 10:20:47 UTC]

hi, freehackers.org site has been updated to fix this bug.
all my fault, sorry

Thomas (freehackers.org webmaster)