#9876: Building PARI/GP with SAGE_CHECK=yes fails on 32-bit big endian machines
------------------------------+---------------------------------------------
   Reporter:  jdemeyer        |       Owner:  tbd                               
     
       Type:  defect          |      Status:  needs_review                      
     
   Priority:  blocker         |   Milestone:  sage-4.6                          
     
  Component:  packages        |    Keywords:                                    
     
     Author:  Jeroen Demeyer  |    Upstream:  Completely fixed; Fix reported 
upstream
   Reviewer:                  |      Merged:                                    
     
Work_issues:                  |  
------------------------------+---------------------------------------------

Old description:

> '''This is an upstream problem with PARI/GP'''
>
> Upstream report: [http://pari.math.u-bordeaux.fr/cgi-
> bin/bugreport.cgi?bug=1099]
>
> The "rnfkummer" test in PARI's {{{make test-all}}} fails on the following
> systems:
>  * PPC OS X 10.4
>  * Linux PPC 32-bit
>  * Solaris sparc
>
> For example, on a PPC Mac OS X 10.4:
> {{{
> GP/PARI CALCULATOR Version 2.4.3 (development svn-12594)
> PowerPC running darwin (PPC/GMP-5.0.1 kernel) 32-bit version
> compiled: Sep  8 2010, gcc-4.5.1 (GCC)
> (readline v5.0 enabled, extended help enabled)
> }}}
>
> I get a failure in rnfkummer (both sta and dyn), I am attaching the dif
> and the output of Configure.
>
>  * '''New pari spkg:'''
> [http://sage.math.washington.edu/home/jdemeyer/spkg/pari-2.4.3.svn-12577.p6.spkg]
> (see also {{{pari.p6.patch}}} below)
>  * '''sagelib patch:''' {{{9876_doctest.patch}}}

New description:

 '''This is an upstream problem with PARI/GP'''

 Upstream report: [http://pari.math.u-bordeaux.fr/cgi-
 bin/bugreport.cgi?bug=1099]

 The "rnfkummer" test in PARI's {{{make test-all}}} fails on the following
 systems:
  * PPC OS X 10.4
  * Linux PPC 32-bit
  * Solaris SPARC

 For example, on a PPC Mac OS X 10.4:
 {{{
 GP/PARI CALCULATOR Version 2.4.3 (development svn-12594)
 PowerPC running darwin (PPC/GMP-5.0.1 kernel) 32-bit version
 compiled: Sep  8 2010, gcc-4.5.1 (GCC)
 (readline v5.0 enabled, extended help enabled)
 }}}

 I get a failure in rnfkummer (both sta and dyn), I am attaching the dif
 and the output of Configure.

  * '''New pari spkg:'''
 
[http://sage.math.washington.edu/home/jdemeyer/spkg/pari-2.4.3.svn-12577.p6.spkg]
 (see also {{{pari.p6.patch}}} below)
  * '''sagelib patch:''' {{{9876_doctest.patch}}}

--

Comment(by leif):

 Jeroen, could you also extend the message printed when
 {{{SAGE_TUNE_PARI=yes}}} to strongly recommend running PARI's test suite
 after tuning? (We could in principle do that automatically from {{{spkg-
 install}}} as well, but that's IMHO not a good idea since it then might
 get run twice, and also doing so wouldn't fit Sage's build/test process.)

 As mentioned somewhere else (#9343?), one of PARI's self-tests fails
 ''after "successful" tuning'' on a Pentium 4 Prescott running Ubuntu 9.04
 (gcc 4.3.3). I've yet only put a comment on the wiki page; will open a
 ticket for that later.

 ----

 I'd prefer prepending {{{./}}} to {{{Configure}}}, since this will give an
 ''appropriate'' error message in any case where {{{src/Configure}}} does
 (for whatever reason) not exist. (Otherwise {{{bash}}} would then attempt
 to find it in {{{$PATH}}}, which might cause weird behavoir.)

 ----

 While adding {{{-fno-common}}} on MacOS X 10.5 and 10.6, too, is perhaps a
 bit odd, it doesn't hurt; otherwise one should look for ''Darwin 8''
 (10.4) with {{{uname ...}}}. (I currently don't know the exact string; the
 relevant part should be the same on PPC 10.4.).

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9876#comment:19>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" 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/sage-trac?hl=en.

Reply via email to