As Ingo B. pointed out, i had to change CFLAGS in make.conf to "-O2", emerge lame and restore CFLAGS to the old values.
Is it worth to create a bug report out of this? Regard, Tim Ruehsen Am Montag, 10. März 2003 15:48 schrieb Tim Ruehsen: > Hi, > > i am about to install V1.4 RC3 on a AMD k6-2 system, but emerging always > stops with 'lame' which is to be compiled within the 'emerge kde' process. > > I already made a 'emerge -u world' which recompiled X11 stuff, but another > 'emerge kde' still results with an error while compiling 'lame'. > > Last lines written on console (putting in here by hand'): > > mv -f -libs/vorbis_interface.lo vorbis_interface.lo > gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I. -I../mpglib/ -I.. -Wall > -march=k6-2 -O3 -pipe -fomit-frame-pointer -c vbrquantize.c -MT > vbrquantize.lo -MD -MP -MF .deps/vbrquantize.TPlo -o vbrquantize.o > > >/dev/null 2>&1 make[3]: *** [vbrquantize.lo] Error 1 > > make[3]: Leaving directory > '/var/tmp/portage/lame-3.93.1-r1/work/lame-3.93.1/libmp3lame' ... some > more make 'Leaving...' mesages ... > > !!! ERROR: media-sound/lame-3.93.1-r1 failed. > !!! Function src_compile, Line 44, Exitcode 2 > !!! (no error message) > > > > Does anybody have an idea how to 'skip' lame or even better how to do that > correctly? > > Regards, Tim Ruehsen > > > -- > [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
