Indeed, memory was the issue. By the way, serendipitiously, linode.com spontaneously upgraded all virtual root boxen to 256M ram for free right around the time I ran into this, which solved the problem. so, if anyone would like to try haskell in a hosted environment, I can now heartily recommend them :) 2007/2/28, Paul Brown <paulrbrown+haskell-cafe@gmail.com>:
On 2/27/07, Seth Gordon <sethg@ropine.com> wrote:
Thomas Hartman wrote:
Thanks. I incorporated these changes, and it cranks longer now before failing. But still fails, now with a seg fault. According to conventional wisdom, when gcc segfaults on a big compilation job (e.g., the Linux kernel), it could be a sign of a transient memory error; gcc exercises the RAM so much that the error rate on a typical computer's memory chips can have a practical effect.
I believe that you're probably correct in this case: I was able to get ghc 6.6 + optional packages built on a linode virtual host (guessing from the original poster's prompt) but only after expanding the amount of memory available.
-- Paul _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe