Does that run android or a complete distribution?
There is a working port if you have a complete distribution ; from the
top of my head, you'll mostly need a newer flint (1.5.2) and that's
all. There will only be a few failing tests.
Snark on #sagemath
Dima
There is that one:
http://trac.sagemath.org/sage_trac/ticket/10285
But I haven't updated it since long!
Snark on #sagemath
Here is the trac ticket about the flint package:
http://trac.sagemath.org/sage_trac/ticket/10328
Snark on #sagemath
Please review it! It needs to be reviewed for changes I made, so
I can't do it myself...
Dima
No, sorry. Perhaps this is where you happen to run out of memory?
I have a new autotools-based release of eclib, which will be turned
into a new spkg after the weekend, and with luck that will settle some
build issues.
John
(eclib author)
>
> And in a related question: is there any compiled tarball of sage for
> arm available somewhere?
>
> --
> To post to this group, send an email to sage-...@googlegroups.com
> To unsubscribe from this group, send an email to sage-devel+...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/sage-devel
> URL: http://www.sagemath.org
> to compile sage. The build process went on pretty far,but eclib keeps
> failing. I get the following error message:
>
> Assembler messages:
> Fatal error: can't create egr_n.o: Input/output error
>
> Any clue about how to solve this?
indeed, it looks like a memory issue. Set up a 1Gb swap or so...
On AC100 ARM subnotebooks similar problems arise.
>
> And in a related question: is there any compiled tarball of sage for
> arm available somewhere?
No, although I guess I can try to make one.
>
I had made one available, but it was ages ago, so the file is probably
not available anymore : my provider's big files service keeps them
around six months after the last download.
Additionally, I can't remember if it was armel or armhf...
Snark on #sagemath
I didn't try building the latest beta.
Could it be a recent update issue?
>
Snark and me are using a newer ubuntu, 11.10.
And no chroot, but a native Linux, with Android wiped out for good.
So it's a fairly different setup. I guess if I compile Sage it would
not run on your setup.
Dmitrii
Assembler messages:
Fatal error: can't create egr_n.o: Input/output error
> On 2012-04-08, mmarco <mma...@unizar.es> wrote:
> > and my chroot environment is ubuntu 9.11 armel.
>
> Snark and me are using a newer ubuntu, 11.10.
and armhf
> And no chroot, but a native Linux, with Android wiped out for good.
> So it's a fairly different setup. I guess if I compile Sage it would
> not run on your setup.
Indeed, I had seen the hardware device, but had not realized android
was still there.
Snark on #sagemath
I am not sure I have armhf, and not armel.
How can I tell for sure?
Dima
I'll dig the documentation to find out how to make one of what I have
(I think it's a 5.0.beta4 or 5.0.beta5), and post a link.
Snark on #sagemath
If you are interested in taking a look, it is at
http://homepages.warwick.ac.uk/staff/J.E.Cremona/ftp/progs/ (NB not
yet an spkg)
John
>
> -leif
I configure-d, make-d and make check-ed it on x86_64 and on ARM : no
problem (and out of tree).
I had a look at the configure.ac ; it looks good, but I still
have two remarks :
(1) "-Wall -Werror" : nifty!
(2) is it even possible that a libm doesn't contain "cos"!?
I also read libsrc/Makefile.am : can't the file listed in
EXTRA_DIST be put in the various *_DOTHS?
In tests/Makefile.am :
(1) same remark about curvesort.cc in EXTRA_DIST ;
(3) the echo commands should perhaps be @echo, so we see the command
result and not the command.
I hope that helps,
Snark on #sagemath
Well, it's only a 4.8 after all : I only had one 5.0beta?? tree left,
and it was in a dubious state. 4.8 is the last which should work (even
though I didn't use it since long :-/)
I ran "./sage -bdist 4.8", then removed the obtained .tar.gz, then
re-made a .tar.bz2 (and it's still big...).
Here it is: http://dl.free.fr/gqloNmzVD
I haven't looked at the new eclib, but please don't use -Werror. Some
devel version of MPC broke because of that, I managed to convince the
MPC developers to remove -Werror. You just don't know which warnings
different versions of gcc will produce on different systems.
I'm all for using -Werror for your own personal development, but don't
use it on everybody's systems.
Sorry that I had not responded to this -- probably eclib issues should
be in another thread.
Although I interpreted your "nifty" as positive, I take Jeroen's point
about not using -Werror, but I'll leave in -Wall.
On 7 April 2012 15:00, Julien Puydt <julien...@laposte.net> wrote:
> Le mardi 10 avril, John Cremona a écrit:
>> If you are interested in taking a look, it is at
>> http://homepages.warwick.ac.uk/staff/J.E.Cremona/ftp/progs/ (NB not
>> yet an spkg)
>
> I configure-d, make-d and make check-ed it on x86_64 and on ARM : no
> problem (and out of tree).
Hooray!
>
> I had a look at the configure.ac ; it looks good, but I still
> have two remarks :
> (1) "-Wall -Werror" : nifty!
> (2) is it even possible that a libm doesn't contain "cos"!?
Perhaps I should take out that test for libm, and also the one for
gmp, since it definitely will not build without a working NTL and pari
(which will be the case with Sage), and eclib does not call gmp
directly.
>
> I also read libsrc/Makefile.am : can't the file listed in
> EXTRA_DIST be put in the various *_DOTHS?
I could rename that variable as (say) extra_includes and add it to the
DOTHS list. They are not header files though.
>
> In tests/Makefile.am :
> (1) same remark about curvesort.cc in EXTRA_DIST ;
OK
> (3) the echo commands should perhaps be @echo, so we see the command
> result and not the command.
I have wondered how to do that for about 25 years, thanks! It never
seemed so serious that I bothered to find out.
>
> I hope that helps,
It certainly does. I'll make a new version and post it. Thanks a lot
for the constructive comments.
John
>
> Snark on #sagemath
>> I also read libsrc/Makefile.am : can't the file listed in
>> EXTRA_DIST be put in the various *_DOTHS?
>
> I could rename that variable as (say) extra_includes and add it to the
> DOTHS list. They are not header files though.
>
The files listed in EXTRA_DIST are needed when building the library,
but not in useing the library. So they need to be in the distributed
files, but need not be noticed by "make install". I'll leave them as
they are.
John
Done: http://homepages.warwick.ac.uk/staff/J.E.Cremona/ftp/progs/eclib-2012-04-10.tar.gz
John
Not yet, sorry. I have had other things to do but hope to get to it in
the next couple of days.
John
I did not look very closely at a related issue in chroot'ed builds in x86,
but it should be possible to make python multiprocessing use some
other approach like pipes in these conditions. What I did to get sage
to build in the Mandriva build system was to "backport" the previous
logic for a single process build:
> --
> To post to this group, send an email to sage-...@googlegroups.com
> To unsubscribe from this group, send an email to sage-devel+...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/sage-devel
> URL: http://www.sagemath.org
Paulo
I did not report back to you but there is now a new eclib spkg at
http://trac.sagemath.org/sage_trac/ticket/10993
John
Good to know the real issue :-) My workaround only works for
missing /dev/shm. Missing /dev/pts on build chroots I managed
to bug at Mandriva sometime ago, to get it properly mounted in
build nodes, otherwise it cannot generate documentation because
gap would fail to start.
> On 24 abr, 18:07, mmarco <mma...@unizar.es> wrote:
>> There is no /dev/shm in my android system. Could it be that this is
>> the problem? If so, is there any hope of solving it?
Paulo