Just a failed emerge that occurred during emerge world. Reproducible: Always Steps to Reproduce: 1.emerge -Davut world (this was when the package tried to emerge) 2. 3. Actual Results: configure: WARNING: If you wanted to set the --build type, don't use --host. If a cross compiler is detected then cross compile mode will be used. configure: loading cache ../.././config.cache configure: error: `CFLAGS' has changed since the previous run: configure: former value: -O3 -march=i686 -maccumulate-outgoing-args -ftrace -pipe -mmmx -msse -msse2 -falign-functions=4 -fforce-addr -mfpmath=sse -fpref ch-loop-arrays -fPIC configure: current value: -O3 -march=i686 -maccumulate-outgoing-args -ftrace -pipe -mmmx -msse -msse2 -falign-functions=4 -fforce-addr -mfpmath=sse -fprefe h-loop-arrays -fPIC configure: error: changes in the environment can compromise the build configure: error: run `make distclean' and/or `rm ../.././config.cache' and st t over configure: error: /bin/sh './configure' failed for util/profile !!! Please attach the config.log to your bug report: !!! /var/tmp/portage/mit-krb5-1.4.1/work/krb5-1.4.1/src/config.log !!! ERROR: app-crypt/mit-krb5-1.4.1 failed. !!! Function econf, Line 485, Exitcode 0 !!! econf failed !!! If you need support, post the topmost build error, NOT this status message Expected Results: Correct emerge =) Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.4.200 41102-r1, 2.6.11-ck10 i686) ================================================================= System uname: 2.6.11-ck10 i686 AMD Athlon(tm) 64 Processor 2800+ Gentoo Base System version 1.6.12 Python: dev-lang/python-2.3.5 [2.3.5 (#1, May 1 2005, 17:27:32)] dev-lang/python: 2.3.5 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.5 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.16 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=i686 -maccumulate-outgoing-args -ftracer -pipe -mmmx -msse -m sse2 -falign-functions=4 -fforce-addr -mfpmath=sse -fprefetch-loop-arrays -fPIC " CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share /config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/ mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/sh are/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/te x/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/init.d /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=i686 -maccumulate-outgoing-args -ftracer -pipe -mmmx -msse -msse2 -falign-functions=4 -fforce-addr -mfpmath=sse -fprefetch-loop-arrays -fP IC" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms strict userpriv usersandbox" GENTOO_MIRRORS="ftp://gentoo.ccccom.com http://gentoo.ccccom.com http://mirrors. tds.net/gentoo ftp://ftp.ussg.iu.edu/pub/linux/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.us.gentoo.org/gentoo-portage" USE="x86 X acl alsa anthy apm arts audiofile avi berkdb bitmap-fonts cdr cjk cry pt cups curl divx4linux doc dvd emboss encode esd faad fam flac foomaticdb fortr an ftp gd gdbm gif gpm gtk gtk2 imagemagick imlib jack java jpeg junit kde kerbe ros ldap libclamav libg++ libwww mad mikmod mime mmx motif mozilla mp3 mpeg mysq l ncurses nls nptl nptlonly oav offensive ogg oggvorbis opengl oss pam pdflib pe rl png ppds python qt quicktime readline sdl slang spell sse ssl svga tcltk tcpd tetex tiff truetype truetype-fonts type1-fonts usb videos vorbis xine xml xml2 xmms xv zlib video_cards_radeon userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS
Remove the double spaces from your C[XX]FLAGS...
You should supply a warning in the ebuild if config fails, or in make.conf.example to avoid this.
*** Bug 103402 has been marked as a duplicate of this bug. ***
