evrey time im traing to install gnome or xfce4 i get dis error gcc: unrecognized option `-03' mv -f xpointer.o .libs/xpointer.lo gcc -DHAVE_CONFIG_H -I. -I. -I. -I./include -I./include -D_REENTRANT -march=athl on -03 -pipe -fomit-frame-pointer -Wall -c xpointer.c >/dev/null 2>&1 mv -f .libs/xpointer.lo xpointer.lo /bin/sh ./libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I. -I./include -I. /include -D_REENTRANT -march=athlon -03 -pipe -fomit-frame-pointer -Wall - c xinclude.c rm -f .libs/xinclude.lo gcc -DHAVE_CONFIG_H -I. -I. -I. -I./include -I./include -D_REENTRANT -march=athl on -03 -pipe -fomit-frame-pointer -Wall -c xinclude.c -fPIC -DPIC gcc: unrecognized option `-03' trionan.c:514: warning: `trio_isfinite' defined but not used trionan.c:742: warning: `trio_fpclassify' defined but not used mv -f xpath.o .libs/xpath.lo gcc -DHAVE_CONFIG_H -I. -I. -I. -I./include -I./include -D_REENTRANT -march=athl on -03 -pipe -fomit-frame-pointer -Wall -c xpath.c >/dev/null 2>&1 mv -f xinclude.o .libs/xinclude.lo gcc -DHAVE_CONFIG_H -I. -I. -I. -I./include -I./include -D_REENTRANT -march=athl on -03 -pipe -fomit-frame-pointer -Wall -c xinclude.c >/dev/null 2>&1 mv -f .libs/xinclude.lo xinclude.lo /bin/sh ./libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I. -I./include -I. /include -D_REENTRANT -march=athlon -03 -pipe -fomit-frame-pointer -Wall - c nanohttp.c rm -f .libs/nanohttp.lo gcc -DHAVE_CONFIG_H -I. -I. -I. -I./include -I./include -D_REENTRANT -march=athl on -03 -pipe -fomit-frame-pointer -Wall -c nanohttp.c -fPIC -DPIC gcc: unrecognized option `-03' nanohttp.c: In function `xmlNanoHTTPConnectAttempt': nanohttp.c:910: `len' undeclared (first use in this function) nanohttp.c:910: (Each undeclared identifier is reported only once nanohttp.c:910: for each function it appears in.) make[2]: *** [nanohttp.lo] Error 1 make[2]: *** Waiting for unfinished jobs.... mv -f .libs/xpath.lo xpath.lo make[2]: Leaving directory `/var/tmp/portage/libxml2-2.5.8/work/libxml2-2.5.8' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/libxml2-2.5.8/work/libxml2-2.5.8' make: *** [all-recursive-am] Error 2 !!! ERROR: dev-libs/libxml2-2.5.8 failed. !!! Function src_compile, Line 34, Exitcode 2 !!! (no error message) Reproducible: Always Steps to Reproduce: 1.emerge gnome 2. i get error 3.
I am having the exact same problem. - pablos@kadrevis.com Portage 2.0.48-r5 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1) ================================================================= System uname: 2.4.20-gentoo-r5 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/usr/portage/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR_OVERLAY="" USE="x86 oss 3dnow apm avi crypt cups encode foomaticdb gif jpeg libg++ libwww mad mikmod mmx mpeg ncurses nls pdflib png qt quicktime spell truetype xml2 xmms xv zlib gtkhtml alsa gdbm berkdb slang readline arts bonobo svga java guile sdl gpm tcpd pam ssl perl python esd imlib oggvorbis gnome gtk kde motif opengl mozilla ldap X" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-mcpu=i686 -03 -pipe" CXXFLAGS="-mcpu=i686 -03 -pipe" ACCEPT_KEYWORDS="x86" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" FEATURES="sandbox ccache"
Some success - I just shut off this line in /etc/make.conf: CFLAGS="-mcpu=i686 -03 -pipe" and libxml2-2.5.8 built just fine after that. I wasn't able to get it to go any other way.
wrong category
here's at least part of your problem - gcc: unrecognized option `-03' that should be -O3, (not -zero3).
VERY strange.. I too had this problem, but I definitely had -O3 instead of -03 in /etc/make.conf.. until I synced and did an update world (and ran into this problem). Then I found to my great surprise that it was in fact a zero in /etc/make.conf. Could something possibly have changed it??! Wouldn't it have broken all over the place on previous ebuilds if had been like that for long? At any rate, changing it back to -03 instead of -O3 in /etc/make.conf fixed it for me.
A coworker just ran into this same exact issue. This is a fresh install that I helped him through just last night (08/19/2003). I walked him through make.conf after booting the machine on its own and it was for sure using -03 (zero-three). After an rsync towards the end of the night he kicked off 'emerge gnome' to have it ready by morning. It failed at libxml2, I checked /etc/make.conf, and sure enough it's been switched to -O3 (capital_Oh-three). Isn't it disturbing that something is accessing /etc/make.conf directly and circumventing the usual etc-update ave.? If the intention is to subtly access make.conf and circumvent the usual triggers, then please check your spelling. I just got laughed at for previously talking about how reliable Gentoo is.
Ack. Sorry. Got the 0(zero) and O(capital_Oh) in the above report backwards. Trying so hard not to get it backwards and... oh well. Again, I only got it backwards in the the post, I still experienced the issue on that machine.
okay, i just emerge libxml2-2.5.8 with -O3 set in my CFLAGS and it definitely emerged fine, nothing was changed to -03. this is indeed a worry, but we really need to pinpoint exactly _where_ in the process this flag is getting changed. if anyone has logs handy (matt?) im quite willing to through them, or worst case, rebuild my second box from scratch in the hope of stumbling across the same problem. any comments? thanks.
On a normal sandboxed system you shouldnt look at libxml2 for the make.conf change. Look at portage, what versions are these users running ? libxml2 just shows the problem by erroring out at a certain point (see how earlier gcc commands just ignore the faulty switch).
well i dunno why it became an 0 instead of O , but i have no clue what to do with this or why this would be libxml's fault. It just seems libxml is one of the few builds that trips over it. closing since i have encountered no further reports.
