On Sun, Dec 19, 2010 at 11:16:10AM -0800, Nolan wrote: > Appears to be some show-stoppers here. > Any suggestions for debugging? || Do I need to rebuild, and at what > point should that start. > > > make[1]: Target `check' not remade because of errors. > make[1]: Leaving directory `/sources/glibc-2.12.1' > make: *** [check] Error 2 > root:/sources/glibc-build# grep Error glibc-check-log > make[2]: *** [/sources/glibc-build/stdio-common/bug22.out] Error 1 > make[1]: *** [stdio-common/test] Error 2 > make[2]: [/sources/glibc-build/posix/annexc.out] Error 1 (ignored) > make[2]: *** [/sources/glibc-build/crypt/sha512c-test.out] Error 1 > make[1]: *** [crypt/tests] Error 2 > make[2]: *** [/sources/glibc-build/nptl/tst-execstack.out] Error 1 > make[1]: *** [nptl/tests] Error 2 > make[2]: *** [/sources/glibc-build/rt/tst-cputimer1.out] Error 1 > make[1]: *** [rt/tests] Error 2 > make[2]: *** [/sources/glibc-build/elf/tst-execstack.out] Error 1 > make[2]: *** [/sources/glibc-build/elf/tst-execstack-needed.out] Error 127 > make[2]: *** [/sources/glibc-build/elf/tst-execstack-prog.out] Error 127 > make[1]: *** [elf/tests] Error2 > make: *** [check] Error 2 > All test had passed up to this point. > > I had what I understood to just be a warning on the 2nd pass of GCC, > which read... > "cp: target `gcc/Makefile.in' is not a directory" That looks like a warning, but just to be sure - did you delete the gcc-4.5.1 and gcc-build directories before you started the 2nd pass of gcc ? (I'm on an older ppc64 system at the moment, with no gcc-4.5.1 logs handy, so I can't check if I had that message). > > If someone can point me in the direction I should go, please do so. :) > nolan
The only failure that looks uncommon is tst-execstack, I'm sure people have occasionally reported sha512c and perhaps bug22, cputimer1. Are you running in a virtual machine (they seem to generate more uncommon errors), or on an uncommon CPU ? If not, what is your host distro ? The only similar errors google finds are from hlfs (hardened lfs) e.g. http://www.mail-archive.com/[email protected]/msg01980.html where Robert guessed it was caused by the grsecurity noexestack option, and in that case it should have been logged to syslog. If that is true for you, ignore that set of execstack errors. For the other errors, I doubt they are showstoppers - more likely, down to a combination of your hardware, your host kernel, and perhaps your host distro. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
