Ken Moffat wrote: > Another question - does the upgraded compiler generally look good ? > Does it stress the hardware more ? > > I'm asking because I didn't get around to successfully building > 4.2.0 except on ppc32 (and that looked very good). Today, I finally > got around to trying to build x86_64-64, but as soon as I chroot I > keep hitting segfaults - I build coreutils at the start of the test > tools (my scripts want to use 'df' for space measurement, but it > isn't installed in the cross-compile) and that segfaults (at > different places) while building headers. Commented that out, got > as far as glibc and again it segfaults pretty quickly, and not at > the same place. > > The output from lm_sensors looked normal (ordinary temperatures), > so I opened it up expecting to find a lot of dust but it was clean. > Then I gave it a short run of memtest86+ (only 3 hours) which was > all fine. I think I'll bring forward an LFS-6.3 test build on that > box, at the moment I'm thinking I must have inadvertently offended > the gods. > The builds I've done so far have worked pretty smoothly, before I committed the change I successfully finished a alpha, x86, x86_64, and x86_64-64 build. I didn't do any in depth testing of the tools, but I installed openssh & wget on each one and could netboot each one. I'll rebuild my x86_64-64 and see if I can break it. If the segfaults seem random, data is probably being corrupt somewhere. Did you check the disk?
GCC 4.2.1 had too many bug fixes to pass up. One in particular that would really affect *LFS. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30052 . The bug has been reopened but the bug is fixed, just memory hungry. _______________________________________________ Clfs-dev mailing list [email protected] http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-dev
