I just tried building Pari against mpir-1.3.0-rc3 with --enable-fat on
32 bit linux, and it worked fine, although for some reason on the
machine I built on I had to manually rename mpir.h to gmp.h. (Perhaps
Jason Moxham can look into why --enable-gmpcompat didn't do this for
me - this is on Cicero Jason).

Perhaps in the case of Sage it is picking up a wrong gmp.h header?
Check that gmp.h in the Sage include directory actually came from
MPIR. If not, rename mpir.h to gmp.h.

Still not sure why that should cause the compiler to segfault though.
That just shouldn't happen.

Bill.

2009/11/13 Bill Hart <[email protected]>:
> The compiler itself segfaulted. I don't see how that can be caused by
> MPIR. You aren't even linking with MPIR at that point. You are only
> including gmp.h whilst compiling something else.
>
> In order to build the MPIR test suite after building MPIR with
> --enable-fat, gmp.h must be included and compiled. So we know the MPIR
> code itself should be ok.
>
> The bug may be triggered when building Pari against some version of
> MPIR, but in this case it is far more likely the bug is elsewhere.
> Certainly there is a bug in gcc irregardless, as compilers are not
> supposed to segfault, no matter how broken the code is you are
> compiling (unless you have some broken environment variables hanging
> around).
>
> Bill.
>
> 2009/11/13 William Stein <[email protected]>:
>>
>> Hi Mike (cc: sage-release),
>>
>> See http://trac.sagemath.org/sage_trac/ticket/7451
>>
>> It turns out that MPIR with enable-fat causes "internal compiler
>> errors" to occur later on when building PARI, evidently.
>>
>> William
>>
>> --
>> 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=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to