On 3/1/06, break thestate <[EMAIL PROTECTED]> wrote: > > === gcc tests === > > Running target unix > FAIL: gcc.c-torture/compile/20001226-1.c -Os (test for excess errors) > FAIL: gcc.c-torture/execute/va-arg-25.c execution, -Os > XPASS: gcc.dg/cpp/cmdlne-dI-M.c scan-file > (^|\\\\n)cmdlne-dI-M.*:[^\\\\n]*cmdlne-dI-M.c > XPASS: gcc.dg/cpp/cmdlne-dM-M.c scan-file > (^|\\\\n)cmdlne-dM-M[^\\\\n]*:[^\\\\n]*cmdlne-dM-M.c > > === gcc Summary === > > # of expected passes 24947 > # of unexpected failures 2 > # of unexpected successes 2 > # of expected failures 68 > # of untested testcases 7 > # of unsupported tests 200 > /sources/gcc-build/gcc/xgcc version 3.4.3
I got va-arg-25.c failure pretty commonly when I was building gcc-3.4.x. I never investigated the cause. I've never seen "gcc.c-torture/compile/20001226-1.c" before, though. I don't know enough to say if those are critical errors or not. If you still have the build directory, you can grovel around and try to determine the cause. If it was me, I'd move on. Maybe you just shouldn't build with -Os since that's common to both failures. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
