3.8.3 build error, compiler segfault

[Gene Heskett]

On Wednesday 27 March 2013 17:57:43 Nils Kassube did opine:

> Gene Heskett wrote:
> > Trying to build a working 3.8.3 kernel, on a *buntu 10.04-4 LTS system
> > here
> > 
> > My usual 'makeit' script didn't report any errors at the end, but the
> > end trace on screen was obviously incomplete.
> > 
> > Adding a few more echo's to the script, and verifying that every line
> > in it was terminated with " && \\r"  I reran it, and see an error
> > that should have stopped it right there, but did not:
> > ==========================
> > 
> >   CC      net/ipv6/icmp.o
> > 
> > net/ipv4/icmp.c:1115: internal compiler error: Segmentation fault
> > Please submit a full bug report,
> > with preprocessed source if appropriate.
> > See <file:///usr/share/doc/gcc-4.4/README.Bugs> for instructions.
> > make[2]: *** [net/ipv4/icmp.o] Error 1
> > make[1]: *** [net/ipv4] Error 2
> > make[1]: *** Waiting for unfinished jobs....
> > 
> >   CC      drivers/md/bitmap.o
> > 
> > ===========================
> > as can be seen it kept marching, the error never made it to bash.
> 
> Maybe you should stop your script in case of errors. You could
> accomplish it if you start the script with this line:
> 
> #!/bin/bash -e
> 
> Anyway, it is a strange fault if the compiler segfaults. Is it
> repeatedly at that particular file? If it isn't, you should probably
> check your RAM.
> 
> And if it is always the same file, you could try a newer version of the
> compiler. If there is none for 10.04 you could use a newer *Ubuntu
> version, possibly in a virtual machine.
> 
> 
> Nils

Gee Nils, that was a week or more ago, and yes it was repeatable on the 
same file, in the bluetooth tree IIRC.

So I backtracked to 3.0.19, and had that work, once.  But now I cannot make 
it work again because every time I touch the .config file with a make 
xconfig, the SOB nukes any and all mention of support for / on an ext4 
formatted drive that needs 'sata_nv' built in as a starter.  Even a make 
oldconfdig using this 2.6.32 kernels .config as a starter is a non-starter, 
falling over because it can't find the root drive's UUID about 4.9 seconds 
into the boot.  Same old same old for 2 newer kernels in between.  Its 
plain to me that something in the "make *config" barn is broken.

And its hell to try and get rid of the modules I don't need, but which take 
another hour to build, with just a 'gedit .config' session.

So ATM I am back on the stock (for linuxcnc) kernel, and swearing at its 
memory collection because with 4G of dram its 500 megs into swap in 3 or 4 
days, running like a plenarium worm at the 25th mile of a marathon, so I 
have to do yet another *^%#$#@ reboot, so my head doesn't hurt so bad.

I have another project going in the shop, and I need to go & get 2 or maybe 
3 basal cell skin cancers excised before much longer, so it will probably 
be 2-4 weeks before I get back to this.

I thought maybe it was something somebody else had already hit and fixed, 
but I guess I'm swimming in uncharted, deep water.

Thanks      .

Cheers, Gene
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
My web page: <http://coyoteden.dyndns-free.com:85/gene> is up!
My views 
<http://www.armchairpatriot.com/What%20Has%20America%20Become.shtml>
He who knows, does not speak.  He who speaks, does not know.
		-- Lao Tsu
I was taught to respect my elders, but its getting 
harder and harder to find any...