chapter 6 glibc - segfault / cvs 01022003

Trent Roaster200 at
Fri Jan 3 08:32:58 PST 2003

Are there any errors produced by binutils?! Especially the
errors, where a file could not be replaced because of permissions.
Do you use special optimization or marchtype?!

Fualty hardware is also an option.
Not only RAM but I had a corrputed harddrive as well as an damaged 
cooler. The one with the cooler was tricky, because with normal routing 
CPU usage there was no problem. When compiling I had several 
segmentation fault, but they are easily to locate (I think):
They occured ecery time at another position. You seem to be on the same 
position: ld and binutils.

Best regards

Willem Oldeman schrieb:
> Could be caused by flaky hardware, especially faulty RAM.
> Google around a bit, there are plenty articles on this one.
> On Friday 03 January 2003 15:48, |Crazor| wrote:
>>everytime i compile the glibc at the end of chapter 6, i get a sigfault
>>when making:
>>gcc -shared -static-libgcc [...] /usr/src/glibc-build/libc_nonshared.a
>>collect2: ld terminated with signal 11 [Segmentation fault], code dumped
>>make [2]: *** [/usr/src/glibc-build/iconvdata/] Error 1
>>make [2]: Leaving directory '/usr/src/glibc-2.3.1/iconvdata'
>>make [1]: *** [iconvdata/others] Error 2
>>make [1]: Leaving directory '/usr/src/glibc-2.3.1'
>>make: *** [all] Error 2
>>binutils version is 2.13.2, also tried already
>>anyone had this error or knows a soulution?
>>thx in advance

Unsubscribe: send email to listar at
and put 'unsubscribe lfs-support' in the subject header of the message

More information about the lfs-support mailing list