Joel Baker <[EMAIL PROTECTED]> writes: > # of expected passes 5176 > # of unexpected failures 1114 > # of expected failures 977 > # of untested testcases 15 > # of unsupported tests 3
Those you should look at, first. gcc creates a detailed log file of all test cases; I don't know whether this survives the Debian build process, though - it's in <objdir>/gcc/testsuite. If you still have that, please post the details for three or four failures (preferably those that make up the majority of the 1000 failures). > This is my current suspect, especially because I have some vague > recollections of a comment that NetBSD native may not have > libgcc_s.so.1 when using GCC 3.x, or somesuch. Though the gcc test > suite seems to work fine, just not the G++ one - is libgcc_s.so only > used for C++? gcc does not link libgcc_s to to C executables, no - only to C++ executables, and to shared libraries (any language). For C, it is sufficient to use the routines from the static libgcc (mostly divdi3 and friends) - the shared library is only needed when the implementations use global variables (mostly for exception handling). Regards, Martin
