I'm having quite some problems building the gcc-core-3.3.1.tar.bz2(chapter 5-LFS 5.0).

Here's what i've done:
date >> sbu; ../gcc-3.3.1/configure --prefix=/tools --with-local-prefix=/tools --disable-nls --enable-shared --enable-languages=c && make BOOT_LDFLAGS="-static" bootstrap && make install; date >> sbu

Everytime i try to build it, it gives an internal compiler error, but never in the same function. I've even removed the bootstrap option, but it still gives the same error...it just appears faster.

I'm using Mandrake 9.0.

Could it be a problem with the compiler?

Well, You are NOT following the book correctly!!
this is done first............then............
this done second, don't add it all on one line........this is not how it
is done in the book...............taking shortcuts like this will
cause alot of errors!!

I'm sorry, but executing commands separated by && is the same thing as doing them individually. The second one will only be executed if the first one is sucessfully completed.

But i'm going to try that anyway.

I still have the problem. In the make BOOT_LDFLAGS="-static" bootstrap instruccion it always gives an internal compiler errror and never in the same function.

Anyone has any ideas?

Does your error message look anything like this http://www.linuxfromscratch.org/lfs/...cannot-find-lc

No, i've already installed glibc-static-devel RPM

Ok, my problem is covered by the LFS-FAQ:
signal 11: (internal error: Segmentation fault), which sugests it may be a hardware problem.
Altough my machine is not overclocked, it tens to heat a lot and it may also be a memory problem, so i'm going to try to solve it.

Has this happened to anyone? And how was it solved?

Thanks.

A little update on the problem. I have tested the two memory modules with memtest86 and found that only one of them has problems and removed the faulty one, but i still can't compile this package as it continues to deliver internal compiler error:segmentation fault on "random" functions.

I've tried on other distribution, same machine, same problem.

Anyone has the same problem?

Problem solved.

It was a hardware problem. The processor was heating too much because it was too dirty, a little cleaning solved everything.