Aaron Cordova wrote:
On Wed, 2005-03-30 at 12:16 -0500, Joel Miller wrote:This is almost always a sign of hardware problems, usually marginal cpu overheat. When my system does this, it's time to blow the dust out of the cpu heatsink.
Aaron Cordova wrote:
I'm not really sure if I have come across this problem before on
this list. But here is the situation. After I have built the static
version of gcc and have chrooted, I get a seg. fault during large
builds. Especially glibc. At first I thought it was my computer and I
read the document listed in the FAQ. But I don't recall having this
problem in chapter 5. So I tested it and I build glibc as a regular user
<snip>
I'm afraid I'm very confused here. You are not supposed to have a statically linked gcc in chapter six. The only statically linked gcc should be the first pass in chapter five. Even then, it gets overwritten by the second pass of gcc in chapter five which is dynamically linked.
-- Registered LFS User 6929 Registered Linux User 298182
Sorry for the confusion, I was exhausted when I initially wrote this email. When I start compiling using a newly built gcc it crashes (seg faults) a whole lot. But the errors don't happen at the same point every time. And always occur after varied times. If I use the gcc that comes with my host system (FC3) I don't get this problem.
Regards,
Kevin
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
