This bug seems to only apply if you have your flags set to k6-2 (or probably k6-3). The following line in the e-build replaces your march and mcpu flags to i586 if they are set to k6[-2, -3]. replace-flags k6-3 i586 replace-flags k6-2 i586 replace-flags k6 i586 However, what happens is your march flag gets changed to i586, but your mcpu flag only gets the k6 portion changed, leaving you with an unrecognised "-2" option. e.g. OLD flags: march=k6-2 mcpu=k6-2 NEW flags: march=i586 mcpu=i586-2 This triggers warnings on every file compiled and leaves you with a broken KDE. Kde cannot start because kdeinit fails to find being unable to find libjpeg.so.62 A quick work around is to comment out the line (21) that says replace-flags k6 i586 this allows the files to compile with march=i586 and mcpu=k6-2. I will learn more about ebuilds and try fix it so that both flags say i586
fixed in cvs -- please try again
i know this is already closed. CHOST="i686-pc-linux-gnu" CFLAGS="-mcpu=k6-2" CXXFLAGS="-mcpu=k6-2" emerge jpeg-6b-r3.ebuild ./libtool --mode=compile gcc -mcpu=i586 -I. -c ./jcapimin.c gcc -mcpu=i586 -I. -c -fPIC -DPIC ./jcapimin.c works fine with replace-flags can we change this back ? makes #16357 invalid
*** Bug 18061 has been marked as a duplicate of this bug. ***
