Subject: Re: curreent build: internal compiler error: Segmentation fault
To: None <email@example.com>
From: C. K. <firstname.lastname@example.org>
Date: 06/04/2007 06:22:16
Yes, it was the same file... That was why i said "same". I will remove obj
and tools dirs and will re-try.
Matthias Scheler-2 wrote:
> On Sun, Jun 03, 2007 at 05:34:45PM -0700, ck74 wrote:
>> It seems there is a problem within source... or at least not memory
>> I have just did "# cd /usr ; cvs checkout -P src" and then tried to
>> and the result is same.
>> Also just after it fails:
>> Memory: 449M Act, 252M Inact, 1208K Wired, 70M Exec, 274M File, 69M Free
>> Swap: 1999M Total, 77M Used, 1922M Free
> Does it always fail on the same file? Or does it fail on random locations
> which change every time you try?
> If it fails and random locations and gets a little bit further everytime
> you invoke "make" (or "build.sh") it is almost certainly a problem
> with the memory in the box.
> GCC is the best memory tester I know. It works much better than "memtest",
> "memtestplus" and all the other tools.
> Kind regards
> Matthias Scheler http://zhadum.org.uk/
View this message in context: http://www.nabble.com/curreent-build%3A-internal-compiler-error%3A-Segmentation-fault-tf3862410.html#a10949710
Sent from the current-users mailing list archive at Nabble.com.