On 02/ 5/11 10:05 AM, Julien PUYDT wrote:
Hi,
I'm the guy who reported and worked on :
http://trac.sagemath.org/sage_trac/ticket/10285
For reference, the problem was that I couldn't get sage 4.6.0 to build
on my ARM-based netbook. I fought hard (and well!), and finally got sage
up -- that required a few changes here and there, getting in touch with
the involved upstream to fix things, etc.
It got up, but it fails a few tests ; I investigated, got an
answer/question, investigated back... and it's been stuck there since a
few weeks now.
Could someone lend a hand?
Snark
It would help if you opened tickets for each particular problem, but have them
linked to one ticket. For example:
http://trac.sagemath.org/sage_trac/ticket/9026
has the issues which are preventing 64-bit builds on Solaris.
http://trac.sagemath.org/sage_trac/ticket/9999
lists problems on AIX.
Reading through the ticket you reference, it is hard to see the wood from the
trees.
I would point out one thing worth noting. Your ticket says "-m32" is an x86
specific option. That is not true. It works on SPARC too and many other platforms.
I'm also aware that on HP-UX (with at least the PA-RISC CPU), one needs to build
a different gcc for 32-bit and 64-bit executables. So whilst gcc can build both
32-bit and 64-bit binaries, you need two copies of gcc. They will not accept
the -m32 or -m64 options.
Is ARM running big endian or little endian? If I understand correctly, it may be
possible to use either mode on those CPUs.
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
Dave
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
