Hi Callum, >> Those results look really bad, but I assume some systematic error. To >> investigate, one would need to look at e.g. gcc/testsuite/gcc/gcc.log to >> see how exactly the tests are failing. > https://sucs.org/~kais58/testsuite/ <https://sucs.org/%7Ekais58/testsuite/> > The entire testsuite directory is here > <https://sucs.org/%7Ekais58/testsuite/> thanks. I see that the fast majority of failures is with compiler exited with status -1 output is: spawn failed I saw them myself at a time, and under par found 11260mS expect(517760): open("/dev/ptmx", O_RDWR, 037777777777) = 8 11261mS expect(517760): stat("/dev/pts/2", 0x7ffae0f0) errno = 2 (No such file or directory) For some reason, ptys weren't created on demand, but had to be created manually since /dev/MAKEDEV had no support for that. I never found out what was wrong, but the problem hasn't bitten me since. >>> Previous build of GCC-4.5.3 to compile it >>> mpfr-3.0.1 >>> gmp-5.0.2 >>> mpc-0.9 >> This might cause problems: I'd stay with the exact versions mentioned in >> the install docs, since I've often seens serious problems with older >> version. > I'll rebuild these and then use them to build gcc-4.6.1 now, do you mean > the minimum required versions ie 2.4.2, 4.3.2, 0.8.1? Exactly. At least on Tru64 UNIX, newer versions even fail their own tests, and we had similar reports e.g. on SPARC. >> Btw., which versions of tcl, tk and dejagnu do you use? I have tcl 8.4, >> expect 5.43.0, and dejagnu 1.4.4. > tcl/tk-8.5.10, expect-5.45, dejgnu-1.5 currently Those should be fine. Rainer -- ----------------------------------------------------------------------------- Rainer Orth, Center for Biotechnology, Bielefeld University
