Hello. OK, you're probably right, it's a hardware problem. It's the most credible explanation, even if the exact circumstances triggering it will remain obscure. I will follow your suggestions and try a step by step compilation, following the script.
Just a precision, this is not I absolutely *want* to compile Sage, but unfortunately I have no choice because there is no suitable binary. The Sage version I currently use (2.11) was compiled by the Sage team, I've never succeed to complete a compilation. However, I have almost reached the goal (64 files in "spkg/ installed"), thus my frustration ! If it happens you can grab the same CPU+OS without hassle and build a binary, I should be very grateful. Anyway, I will strive to finish a compilation on my own if you can't provide it. Thanks again for your support ! PS. My OS/environment is : Debian Etch + gcc-4.1.2 and "cat /proc/cpuinfo" returns : ------------------------------------------------------------------------------- processor : 0 vendor_id : AuthenticAMD cpu family : 6 model : 2 model name : AMD Athlon(tm) Processor stepping : 1 cpu MHz : 808.004 cache size : 512 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx fxsr syscall mmxext 3dnowext 3dnow up bogomips : 1617.52 ------------------------------------------------------------------------------- --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
