[uClibc] buildroot, toolchain or root_fs?

[Henri van Riel]

Hello Carl,

Wednesday, May 5, 2004, 5:16:55 PM, you wrote:

CM> On Wed, May 05, 2004 at 02:58:04PM +0200, Henri van Riel wrote:
>> 
>> I've build gcc-3.3.2 now. I had 1 segmentation fault during the build.
>> 
>> The workaround for that seems to be to go into the directory where it
>> failed and type `make <program-it-was-trying-to-compile>.o`. Chances
>> are it will compile without a problem and then return to top-level and
>> type `make` again. Compilation will continue where it left off...
>> 
>> I'm now trying to build buildroot but I had 2 segfault so far. I did
>> the same trick as described above and it's still going. Obviously the
>> segfaults don't have much to do with the gcc version.

CM> That sounds like the infamous "gcc fatal sig11" bug.  Which isn't a
CM> software bug in gcc.  It's a hardware bug.  It turns out that using
CM> gcc to compile large, complex packages is a better memory tester than
CM> most dedicated memory testers.  If you get unexplained segfaults in
CM> gcc that appear and disappear at random given the same input files and
CM> compilation flags, you should suspect that you have marginally flaky
CM> memory on your box.  Try replacing it with higher-quality, faster-rated,
CM> or better-cooled (or any combination thereof) RAM bricks and see if the
CM> problem clears up.

I was thinking the same thing! Problem is, I don't have other RAM
bricks to try, these will have to do for now :(

I *really* do need new hardware....

Thanks for the reply!

-- 
Henri.