On 02/11/11 12:46 AM, Francois Bissey wrote:
On 10 February 2011 20:59, Francois Bissey
It appears this was a bug created by ECL which the ECL developer has
acknowledged
http://www.mail-archive.com/ecls-list@lists.sourceforge.net/msg00671.html
and is fixed in CVS. So I think we should leave Maxima untouched, and
instead apply a patch to ECL
What is not clear from that posting is where in the ECL code the bug
is, but clearly this is an ECL bug, and may cause other issues we are
so far unaware of.
Agreed. I'd say from the date stamp and description:
http://ecls.git.sourceforge.net/git/gitweb.cgi?p=ecls/ecl;a=commit;h=ce19c6
7a1b9f63cd232e7c0a621b6ca87aaa7214
That's the right patch. Patched ecl-11.1.1, build, unpatch maxima, build.
Test:
maxima
;;; Loading #P"/usr/lib64/ecl-11.1.1/sb-bsd-sockets.fas"
;;; Loading #P"/usr/lib64/ecl-11.1.1/sockets.fas"
;;; Loading #P"/usr/lib64/ecl-11.1.1/defsystem.fas"
;;; Loading #P"/usr/lib64/ecl-11.1.1/cmp.fas"
Maxima 5.23.2 http://maxima.sourceforge.net
using Lisp ECL 11.1.1
Distributed under the GNU Public License. See the file COPYING.
Dedicated to the memory of William Schelter.
The function bug_report() provides bug reporting information.
(%i1) next_prime(113);
(%o1) 127
Which is what we want. Now to test my own doctest patch.
Francois
Can you post a link to your .spkg since you have created one.
I assume you are using 'patch' rather than 'cp' to copy the files over, since
'patch' has been added to Sage.
I guess a ticket should be created to update Maxima too. It looks like it would
be sensible to update the two together, though its best if they are on two
tickets, as it will make the review easier.
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
