Compiling GCC for an i486

[RMD]

I need to compile gcc-2.95.3 and glibc-2.2.5 on a 686 machine, for a i486
target.

In LFS33 documentation, it says: "This package is known to behave badly when
you have changed it´s default optimization flags (including the -march
and -mcpu options), GLIBC is best left alone, so we recommend you unsetting
CFLAGS, CXXFLAGS and other such variables/settings that would change the
default optimization values it comes with. Also, dont pass
the --enable-kernel option to the configure script. It´s known to cause
segmentation faults when other packages like fileutils, make and tar are
linked against it"
The same words are used for GCC...
This remains true? If so, how can I build gcc and glibc on a pentium-class
machine
for another x86 target?
regards


Ricardo Derbes
Altec SE
Albarracín 157 - San Carlos de Bariloche
+54-2944-426892
rmd@altec.com.ar
----- Original Message -----
From: "Robert Love" <rlove@neosoft.com>
To: "zhenggen" <zhenggen@public1.ptt.js.cn>
Cc: <gcc-help@gcc.gnu.org>
Sent: Tuesday, July 02, 2002 3:26 PM
Subject: Re: Ada compiler built but not working


>
> On Tuesday, July 2, 2002, at 09:01  AM, zhenggen wrote:
>
> > Robert Love wrote:
> >
> >>
> >> gnatmake hello.adb
> >> gcc -c hello.adb
> >> gcc: hello.adb: Ada compiler not installed on this system
> >> gnatmake: "hello.ali" WARNING: ALI or object file not found after
> >> compile
> >> gnatmake: "hello.adb" compilation error.
> >>
> > You should check which gcc you have invoked by shell command "which" :
> > $ which gcc
> > From the message one can figure out that the old  gcc which is located
> > in /usr/bin is called.
> > The work around is put "/usr/local/bin" at the begin of your PATH
> > variable.
>
> Of course you were correct.  My history list shows I had even performed
> a which on gnatmake but not on gcc.  Thank you for clearing up my
> confusion.
>
>
>
> Bob Love mail:  rlove@neosoft.com
> jabber: rlove@jabber.org