Le 24/12/2012 12:53, Martin Albrecht a écrit :
I am pretty sure you're stuck in conversion.c which is a pretty dumb file actually which translates bitpacked representations to bitsliced, it's just bit fiddling but unrolled which probably explains the huge demand for compiling. How much RAM do you have? I could try to limit my RAM on my machine and split up the file so GCC compiles it with that RAM limit. Alternatively, try reducing the -O level.
It would be nice to split that file indeed, because it makes it quite painful to compile sage on the box I use (and probably on others, though I guess one feels it less on more powerful boxes): I have to basically make the box only run the make command (shutdown X and a few other things...)!
I will probably make a bdist of sage 5.5 available in a few days ; I'll try to finish compiling libm4rie (well, conversion.c ...) then I'll need the box for other things than compiling. Then atlas will come...
Cheers, Snark on #sagemath -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
