-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Malcolm Wallace wrote:
You say that your gcc gives random crashes. My best guess is flaky hardware - bad memory.
Yes, I know that's the usual theory, I've run memory tests and haven't detected any. Maybe gcc is buggy and corrupts its stack unpredictably. Although that could just as well produce incorrect results sometimes, I suppose. As a reference point, my machine is a Yhc buildbot and that seems to work fine when gcc (called by ghc) doesn't outright crash. Hmm... compiling with -O3 with "gcc (GCC) 4.1.2 20060928 (prerelease) (Ubuntu 4.1.1-13ubuntu5)" things (including bits of GMP) maybe isn't quite safe? Apparently C compilers are unreliable enough these days that "It has now come to the point where a compiler should be assumed to miscompile GMP." http://gmplib.org/ and "It might seem that GMP is unusually unlucky with compilers, that it triggers more bugs than other packages. I believe that is an illusion. What really is happening, is that GMP has a test suite that will find almost every miscompilation in the library." http://gmplib.org/list-archives/gmp-bugs/2007-February/000698.html
Maybe there was some random corruption in gcc whilst building something in the runtime system. I would try rm targets/powerpc-Darwin8/obj/runtime rm targets/powerpc-Darwin8/runtime make runtime and see if you get the same behaviour.
rm -r targets/ppc-Linux/obj/runtime/ rm targets/ppc-Linux/runtime make runtime make install This didn't help. BTW my --prefix=/home/isaac/install/nhc98 (and I haven't put that/bin in my PATH) Isaac -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF6LO5HgcxvIWYTTURAnnvAKCB1Oq3irRKx8ZyTEibfpmoqWSYmwCgvIqK P1WL7QS06iBHkdCMp5s72Fk= =5wWy -----END PGP SIGNATURE-----