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
I think I got the image working with the linux app I've been using
(Complete Linux Installer), so I'll give Sage a try tomorrow or Sunday.
--
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@googlegroup
I didn't have any luck getting the scripts to work with a basic image I
built. Does the image have to be in /sdcard/ubuntu (I replaced
/sdcard/ubuntu with /data/sdext2/ubuntu in the scripts, but I'm not sure if
more has to be done)? Do the scripts need something specific to the image
you prov
Ah, that's a pity. It was too beautyful to be true: the possibility to
deliver a sage android app that does not require to hack your device.
On 21 dic, 19:36, Volker Braun wrote:
> fakechroot is a LD_PRELOAD hack that overrides glibc calls and e.g.
> redirects file open() calls. Though its not pe
fakechroot is a LD_PRELOAD hack that overrides glibc calls and e.g.
redirects file open() calls. Though its not perfect, for example no
pseudo-ttys (I think this already rules out Sage).
On Friday, December 21, 2012 6:19:48 PM UTC, mmarco wrote:
>
> I have seen that there is an android app that
I have seen that there is an android app that runs an ubuntu desktop
without the need of root access. From the web page, i see that it uses
something called fakechroot. I would like to investigate that
possibility. Maybe it could be the open door to some nice android app
that would install sage to
mmarco,
Things got pretty crazy and I haven't had a chance to take a look yet, but
I should be able to give it a try in the next day or two. Thank you again
for your help.
On Thursday, December 13, 2012 6:35:52 AM UTC-5, mmarco wrote:
>
> jaebond, did you try the image i linked? did it work fo
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
Hey, yo;
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 freez
jaebond, did you try the image i linked? did it work for you?
On 9 dic, 10:56, mmarco wrote:
> I have made a zip archive with both the image and the scripts that i
> use. you can download it from:
>
> http://riemann.unizar.es/algebra/Archive1.zip
>
> It also includes a readme.txt file
>
> On 8 di
I have made a zip archive with both the image and the scripts that i
use. you can download it from:
http://riemann.unizar.es/algebra/Archive1.zip
It also includes a readme.txt file
On 8 dic, 23:01, jaebond wrote:
> Thank you for that, that will help a lot. I would be interested in the 7gb
> fi
Thank you for that, that will help a lot. I would be interested in the 7gb
file. How do you chroot into your images, do you use a script or an app?
I have been using an app, but it doesn't seem to like images that weren't
made by the app.
On Saturday, December 8, 2012 9:22:20 AM UTC-5, mmarc
Thank you for all of that, it should help a lot. I would be interested in
the 7GB file.
On Saturday, December 8, 2012 9:22:20 AM UTC-5, mmarco wrote:
>
> The problem was that the ubuntu image that i was using was armel
> architecture, but the sage distribution made by Julien was compiled in
>
Thank you for that, that should help a lot. I would be interested in your
7gb file. Do you have a script for chrooting into your images or do you
use an app?
On Saturday, December 8, 2012 9:22:20 AM UTC-5, mmarco wrote:
>
> The problem was that the ubuntu image that i was using was armel
> ar
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
The problem was that the ubuntu image that i was using was armel
architecture, but the sage distribution made by Julien was compiled in
an armhf environment (a slightly different architecture). So there
were not compatible.
My solution was to get an armhf rootfs from the ubuntu core site
(http://
mmarco,
I had been working on this exact same issue a few months ago. Would you
mind explaining what you did to fix your issue?
On Friday, December 7, 2012 7:55:55 AM UTC-5, mmarco wrote:
>
> Nevermind, i found the problem: i had to use an armhf ubuntu.
>
> On 7 dic, 13:15, mmarco wrote:
> >
Nevermind, i found the problem: i had to use an armhf ubuntu.
On 7 dic, 13:15, mmarco wrote:
> I have tried your package in a chroot environment (actually in two, a
> full ubuntu and a lubuntu), and it doesn't start in neither of them.
>
> Stranegly, the problem seems to be different: in the lubu
I have tried your package in a chroot environment (actually in two, a
full ubuntu and a lubuntu), and it doesn't start in neither of them.
Stranegly, the problem seems to be different: in the lubuntu case, it
just shows the message with the version and quits. In the full ubuntu,
it complains with
On 2012-11-17, Julien Puydt wrote:
>
> The internal storage is small, but since it's possible to stick a big SD
> in, that could fly (I need about 5Go for a system, 7Go for sage [did I
> mention it's too much?] and 20Go [mostly] static storage).
>
> Now I'll only
> (1) make sure it can run ubunt
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
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 this purpose in mind. And i
guess that pr
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
On 2012-11-16, Julien Puydt wrote:
> 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
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
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)
On 16 nov, 17:07, Julien Puydt wrote:
> Le 16/11/2012 16:53, mmarco
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
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).
Later i tested version 5.1 over a very minimal newer version
33 matches
Mail list logo
