On Sun, Nov 15, 2009 at 9:45 AM, Jason Moxham <[email protected]> wrote:
>
> 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

I just decided to look into
http://trac.sagemath.org/sage_trac/ticket/7471 and try to actually fix
our patches.  However, we don't patch mpir at all -- we just include
plain vanilla upstream sources.  The mpir spkg was got by just taking
the mpir tar ball from the mpir website, and extracting it into the
src/ subdirectory.  So the discrepancy above must be because of
getting a prerelease version of the tarball.

Anyway, I just want to point out that it wasn't a problem with just
forgetting to update some patches (as I suggested), since we have no
patches.  We used to have tons with GMP, which is why I so quickly
thought we had them still with MPIR.

The only patch-like thing we do when building MPIR is:

    echo "Deleting assembly files which depend on PIC assembly working
or 32 bit OSX on Intel hardware"
    rm mpn/x86/dive_1.asm
    rm mpn/x86/diveby3.asm
    rm mpn/x86/pentium4/sse2/dive_1.asm
    rm mpn/x86/pentium4/sse2/mode1o.asm
    rm mpn/x86/pentium4/sse2/diveby3.asm
    rm mpn/x86/pentium4/mmx/popham.asm
    rm mpn/x86/pentium4/mmx/rshift.asm
    rm mpn/x86/p6/mode1o.asm
    rm mpn/x86/p6/dive_1.asm
    rm mpn/x86/pentium/hamdist.asm
    rm mpn/x86/pentium/mod_1.asm
    rm mpn/x86/pentium/popcount.asm
    rm mpn/x86/pentium/mode1o.asm
    rm mpn/x86/pentium/dive_1.asm


-- 
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org

--

You received this message because you are subscribed to the Google Groups 
"mpir-devel" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/mpir-devel?hl=.


Reply via email to