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 yo
And I'm on a truly measly 256mb of RAM, but with 2gb swap.
Thanks for taking some time to consider this!
On Monday, December 24, 2012 2:53:56 PM UTC+3, Martin Albrecht wrote:
>
> On Monday 24 Dec 2012, tom d wrote:
> > Man, still no success in getting through the libm4rie build. It ran for
> 3
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 con
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 af
Le 24/12/2012 11:28, tom d a écrit :
Man, still no success in getting through the libm4rie build.
I think we should report it as a bug upstream.
Snark on #sagemath
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To post to this group, send ema
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
hap
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 minute
Le 07/12/2012 23:46, jaebond a écrit :
I had been working on this exact same issue a few months ago. Would you
mind explaining what you did to fix your issue?
To explain a bit more: there are several arm flavours, the armel and the
armhf. The -el stands for "endian-little" (a pun), the -hf for
Le 17/11/2012 12:03, mmarco a écrit :
It was a TF 201
Oh, and btw, i think the real bottleneck with it was not the
processor, but the disk access. The processor is not bad (but again,
it can overheat), but the access to the internal sd disk is too slow.
Definitely, not a machine designed with t
Le 17/11/2012 10:13, Dima Pasechnik a écrit :
IMHO Samsung's new ARM Chromebook is what you might want; unfortunately
the internal SSD is small, only 16GB (like on AC100), but 1.7GHz
dual-core Cortex A15. (and 12"(?) screen)
http://www.chromium.org/chromium-os/developer-information-for-chrome-o
Le 16/11/2012 18:58, mmarco a écrit :
Well, the main problem was overheating. Compilation failed several
times, the device turned off by itself. I even think it got damaged,
since the power button stopped working properly (luckily asus was kind
enough to replace it)
Ouch. Bad, very bad, extreme
Le 16/11/2012 16:53, mmarco a écrit :
I run sage on my tablet (asus transformer prime) precisely in that
way: over a ubuntu chroot. I have an old version installed though. I
have an ubuntu 10 chroot, where i compiled sage 4.8 (it was a pain:
over a week of comilation time).
What!? *A week*!?
I
12 matches
Mail list logo
