Re: [Pan-users] compile error on Natty Ubuntu

[Duncan]

Ron Johnson posted on Tue, 14 Jun 2011 08:56:40 -0500 as excerpted:

> What gcc version are you using in Natty?
> 
> On 06/14/2011 08:02 AM, Bob Kowalski wrote:
>> I'm getting the following error when I try to compile Pan .135:
>>
>>
>> CXX adaptable-set-test.o
>>
>> adaptable-set-test.cc: In function ‘int main()’:
>>
>> adaptable-set-test.cc:322:1: internal compiler error: Segmentation
>> fault
>>
>> Please submit a full bug report,
>>
>> with preprocessed source if appropriate.
>>
>> See <file:///usr/share/doc/gcc-4.5/README.Bugs> for instructions.

Grrr! Upside down posting before the quote!  One would think we'd not 
have to worry about that on a pan list, of /all/ places!

Anyway, obviously it's gcc 4.5.something, based on that last line.

Meanwhile, Bob, from my experience on Gentoo (which means I do a *LOT* of 
compiling!), "internal compiler error" often translates as "hardware 
instability error".  Otherwise, the error is normally something else, NOT 
"internal compiler error", with gcc itself segfaulting.

If you've not done so already, please try clearing the build dir and 
rebuilding.  If you don't get an error, or get one but in a different 
place, it's very likely a hardware issue, overclocking, undervolting, bad 
memory, bad power supply, bad memory bus, bad CPU, all of these are 
possibilities.

If however you get the same error at exactly the same spot, starting with 
a clean build dir and source tarball, then and only then is it likely a 
gcc error, and even then, it's most likely an Ubuntu or Debian patch 
introducing the error.  Very very seldom have I seen gcc itself 
segfaulting, except when the hardware itself is the problem.

Of course the hardware error could be as random as a cosmic ray passing 
by and bitflipping the wrong bit of memory at just the wrong moment.  
Individually, it's nothing to worry /too/ much about.  It's only when 
such things become common that it's time to start trying to figure out 
where the hardware problem is.  That's why I said try to repeat it from a 
clean build dir.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman