>
> 2009/11/15 Jason Moxham <ja...@njkfrudils.plus.com>:
>>
>> Solved???
>>
>> jasonmox...@debian5-32:/tmp/jason/mpir-1.2$ diff  config.guess
>> ../sage-4.2.1/spkg/standard/mpir-1.2.p9/src/config.guess
>> 660c660
>> < i?86-*-*|x86_64-*-*|amd64-*-*)
>> ---
>>> i?86-*-*|x86_64-*-*)
>> 755c755
>> <   rm -f ${dummy}032.s ${dummy}32.o ${dummy}32.c ${dummy}032.o ${dummy}064.s
>> ${dummy}64.o ${dummy}64.c ${dummy}064.o $dummy ${dummy}.exe
>> ---
>>>   rm -f ${dummy}032.s ${dummy}32.o ${dummy}32.c ${dummy}032.o ${dummy}064.s
>> ${dummy}64.o ${dummy}64.c ${dummy}064.o $dummy
>> jasonmox...@debian5-32:/tmp/jason/mpir-1.2$ diff  mpn/x86/fat/fat.c
>> ../sage-4.2.1/spkg/standard/mpir-1.2.p9/src/mpn/x86/fat/fat.c
>> 141d140
>> <   __MPN(divrem_euclidean_qr_2_init),
>>
>> and perhaps some others ?
>> Please update sage mpir-1.2 with current mpir-1.2

Excellent, thanks for tracking this down!

Now, I wonder what idiot messed up Sage's mpir-1.2 spkg by not
updating the patches properly?

[... checks SPKG.txt ...]


=== mpir-1.2 (William Stein, May 31, 2009) ===
 * Update to the latest MPIR 1.2 pre-release
 * Change "GMP" --> "MPIR" in various places.

Doh.   That was really dumb.


2009/11/15 Bill Hart <goodwillh...@googlemail.com>:
>
> I probably should put mpir-1.2.2 up actually, as it contained a
> FreeBSD fix specifically for Sage.
>
> I'll have to update the gplv3.txt and license info for mpf/set_str.c though.
>
> Give me a few minutes and I'll do it.

Thanks.   I can't work on this further until tonight because my
internet connection is so horrible.

Anyway, from the Sage side the trac ticket for this is:

http://trac.sagemath.org/sage_trac/ticket/7471

William

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to