Jeremy Huntwork wrote: > [EMAIL PROTECTED] wrote: >> -<screen><userinput>sed -i 's/-O2/-O/' MCONFIG</userinput></screen> >> +<screen><userinput>sed -i 's/-O2/-O/' configure</userinput></screen> > > Just for the sake of thoroughness, here... Please note that the above > sed does *not* remove the use of '-O2' from the compile arguments. > > Here's a sample line from one of my logs when applying the change to > only 'configure': > > "cc -pipe -O2 -mtune=i486 -fomit-frame-pointer -I../lib -Wall > -Wmissing-prototypes -Wstrict-prototypes -DNCH=1 > -D_FILE_OFFSET_BITS=64 -DSBINDIR=\"/sbin\" -DUSRSBINDIR=\"/usr/sbin\" > -DLOGDIR=\"/var/log\" -DVARPATH=\"/var\" > -DLOCALEDIR=\"/usr/share/locale\" -O -s ul.o -o ul -lncurses"
Last one wins. In other words, on the GCC command line, switches that come after override any that come before. The above will achieve the desired result. I'm sure this is documented somewhere but I cannot find the reference right now :-/ > This, as mentioned by Chris, avoids the segfault, but perhaps we should > make sure that -O2 isn't used at all until we know what is causing the > bug? Better still, we should just find the bug and fix it. Why pessimize the whole of Util-linux just because of an intermittent bug in cfdisk? It's a bad workaround IMHO. Surely someone who is able to reproduce the crash can obtain a backtrace so we at least know where to start looking? Regards Greg -- http://www.diy-linux.org/ -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
