computer crashed 3 times while compiling Sagemath (FC8 x86_64)

i have been trying to install sage ( www.sagemath.org ) on FC8.x86_64

# tar -vxf sage*.tar
# cd sage...
# make

the first time 'make' ran about 20 min with several programs running in init 5. the second time it was running in init 5 on its own. the third time i tried running it in init 3.

the two second times i ran

[code]
# rm -rf sage*
# tar -vxf sage*.tar
[\CODE]

to clean it up.

every time i ran 'make' the computer lasted a shorter time than previous.

perhaps i am not cleaning up properly, but i would hope that there is an explanation. Any help on how to properly clean after a crash, or how to get sage running would be much appreciated.

Thanks in advance
-- Flibble

[Prometheum]

The system itself crashes, or make exits with an error?

make shouldn't be able to bring down your system, though it may make it very nonresponsive. Are your discs being accessed?

the whole system goes down, my computer screen freezes and keyboard locks up. i assume that my disks are being accessed because i am compiling from files on the hard drive.

[Prometheum]

make shouldn't be able to do that on its own. Can you light the numlock key if you're doing it from a tty, or are your disk access lights blinking? If so, then it probably isn't the whole system.

Maybe you should try completely cleaning out the build folder, redownloading the source, and starting from scratch. I've never heard of just make or gcc crashing an entire system before.

... i downloaded the source again and deleted the old files
and the same thing happened... any ideas?

[Prometheum]

No, no ideas at all. You can build other things, right?

i can buildother things fine

from the changelog

Thu Sep 22 02:40:33 2005
------------------------
0.7.2: Fixed it so sage path is correct after startup (this is only a
problem when one uses "make install").


You are not using 0.7.2 are you?


And

# QUESTION: When I compile Sage my computer beeps and shuts down or hangs.
# ANSWER: Compiling Sage is quite taxing on the CPU. The above behavior usually indicates that your computer has overheated. In many cases this can be fixed by cleaning the CPU fan and assuring proper ventilation of the system. Please ask you system administrator or a professional to do this in case you have never done this since you can potentially damage your system.


is the only other case I can find. And its its on the FAQ/wiki