On Mon, Dec 20, 2010 at 05:27:09PM -0500, Mike Hollis wrote: > I started a new jhalfs build last night and it failed unexpectedly at > expect. It was late , so I deferred until this am and started over. > > The answer was found accidentally while looking at changelog of the > Version SVN-20101219 . I updated my jhalfs svn and it went forward and > is compiling 077-gcc now , so hopefully there will no more problems. > > Mike Hollis > > Well, I had something I haven't seen before. I got a segfault during the the make -k check printed to the console.
fail31-frag.exe[26552]: segfault at 4 ip 080487cf sp 00000004 error 4 in fail31-frag.exe[8048000+1000] It continued on however but exited on the vim test. I tried the check manually (really a strange looking test with all the flashing and colors) and it failed again. The gcc test looked suspicious, had some doubling of the summaries, and 6 failures other than the 13 lidmudflap . Unfortunately I deleted the the the sources and jhalfs directories before booting. Gcc seems to work allright. I compiled lynx,gpm,dejanu,tcl,expect and set ulimit -s 16384 and ulimit -c unlimited and compiled gcc again. I didn't observe the segfault as I went to bed after watching the lunar eclipse. Luckily we had clear skies here in North Carolina and it was spectacular. The segfault was there in the kernel log and a core was in gcc-build/gcc/testsuite/gcc but I don't know how to call this core with gdb (gdb make core ? gdb gcc core ?) and even if I did it would probably not be useful for me. So , I'm kind of stuck. I don't want to start BLFSing and find a problem later.BTW, the gcc test summary was normal this time. --- Mike Hollis --- -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
