RELENG_6 does not compile
Sten Daniel Sørsdal
lists at wm-access.no
Sat Sep 23 20:16:54 PDT 2006
> Kent Stewart wrote:
>> On Thursday 21 September 2006 18:20, Joerg Pernfuss wrote:
>>> On Fri, 22 Sep 2006 02:59:53 +0200
>>> martinko <martinkov at pobox.sk> wrote:
>>>>>> internal compiler error: Segmentation fault: 11
>>>>>> Please submit a full bug report,
>>>>>> with preprocessed source if appropriate.
>>>>>> See <URL:http://gcc.gnu.org/bugs.html> for instructions.
>>>>>> *** Error code 1
>>>>> Chances are you have failing hardware.
>>>> you must be kidding! :-o
>>>> no, really, this is a laptop and i hope it's not going to die or
>>>> something. :-/
>>>> well, it would actually be better now before the warranty is over.
>>>> ;-) anyway, how did you come to your conclusion pls ??
>>> SegFault 11 is normally a strong indicator of dying RAM.
>> But in a laptop it could be related to heat such as a clogged heatsink
>> or the equivalent. In one of my AMD desktop, I blew the dust out of the
>> heat sink and the cpu temp dropped 5oC. There is a list of causes in
>> the FAQ and they can all be the cause.
> i booted up knoppix and ran memtest for 4 hours (std test), then all
> tests for 8 hrs (6 passes), and no error was reported.
> i searched log for hdd failure messages as mentioned in a thread from a
> few days ago and did not find anything.
> my laptop temperature did not exceed the usual level. i haven't had any
> issue regarding this yet. (nearly two years)
> i wonder what else i could check or what other tests i could run.
> any ideas pls ?
> ps: i'll try to locate the FAQ mentioned above.
Does the error ocurr at different times in the build process or does the
build process stop at the same place?
I've had similar problems when the .so's already installed in the system
was not correct or corrupt. So something i did 3 months earlier out of
boredom cost me half a day of tracking it down (i'm no wiz).
Buildworld always stopped at the same location when this happened (with
a signal 11)
Sten Daniel Sørsdal
More information about the freebsd-stable