Le 19/12/2012 21:52, tom d a écrit :
I'm experimenting with building Sage on the Raspberry Pi. It apparently has an ARM6 processor, so I'm running from scratch. I ran into problems building libm4rie as well (and also on building conversion.c); it would start running and then after about 20 minutes the device would freeze up and my ssh session (since I'm running headless!) would seize up. Nothing I can find in the log files; seems like just a straight out crash. I'm trying again from the beginning in case something went wrong earlier in the build process.
Yes, that one file is a problem.
ATLAS took 807 minutes to compile on the first attempt. I seem to recall hearing that ATLAS has some kind of processor database at some point? I poked around looking for whether there's a good way to store the timings, etc, and chop down the ATLAS compile time but wasn't immediately able to turn any answers up. Anyone have a good idea of where to look?
apt-get install libatlas-dev (or something like this), then export SAGE_ATLAS_LIB=/usr that way atlas won't get compiled in sage. 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.
