________________________________ From: [EMAIL PROTECTED] on behalf of Andy Bennett Sent: Thu 8/30/2007 7:27 PM To: lfs-support@linuxfromscratch.org Subject: Re: i486 Compilation and glibc
Hi, >>> I've tried setting -mcpu=i486 in CFLAGS and CXXFLAGS but the glibc build >>> whinges that it's deprecated and produces the same errors as before. >>> >>> I have gcc 4.0.3. >>> Is it still the case that gcc will produce i386 code by default? Does >>> this apply to the glibc build system? > > I honestly have never tried it and am going to show my ignorance here, > but I would try passing --with-arch=i486 to all the gcc builds. I > believe that will make gcc compile 486 code by default. This is > actually needed on very new glibc as it won't build on 386 anymore. Thanks for your suggestions. I'm not really interested in my i386 anymore. My i486 is more interesting because it has gobs of RAM (128MB). Is --with-arch=i486 a directive to the builds *of* gcc or the builds *with* gcc? Surely it's the former? Is it worth doing chapt5 again with that change in place? Many thanks. Regards, @ndy -- [EMAIL PROTECTED] http://www.ashurst.eu.org/ I think I read somewhere that older CHOST variables were incompatible with nwere versions of gcc.... Could it be that those incompatibilities are occurring because of your CHOST, or even being triggered by your build settings? -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
<<winmail.dat>>
-- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
