> 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? Hi Snark,
That's a very impressive work and I am thinking of looking at it on my nokia N900. Not sure where you precision problem originates, for some numerical tests the expected answers are a bit too precise in my opinion but gamma should be relatively straightforward. So gamma could be called from C, Cython, possibly mpmath, pynac or maxima. I guess you could tests the results calling from mpmath or maxima. I am guessing that SR(10.0r).gamma() will end up being a call to maxima to compute gamma but I could be completely off track. But since it is also a gamma computation it could be related to the previous computation of gamma(6). The pickling is strange, do you use sage's python or have you tried to use the python shipped with your platform? Francois This email may be confidential and subject to legal privilege, it may not reflect the views of the University of Canterbury, and it is not guaranteed to be virus free. If you are not an intended recipient, please notify the sender immediately and erase all copies of the message and any attachments. Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more information. -- 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
