Le 24/12/2012 12:53, Martin Albrecht a écrit :
On Monday 24 Dec 2012, tom d wrote:
Man, still no success in getting through the libm4rie build. It ran for 38
hours before I had to get ready to head back to North America (which
involved cutting power to the Pi). It looks like the swap (on a connected
usb drive) just got so jammed up after a couple hours that the work was
happening at a truly glacial pace: cpu usage was basically zero, with 98+%
of the cpu time spent 'waiting,' according to top.
Hi, M4RIE developer here.
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.
RAM: 512M
Swap: 1G
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.
