#12315: OS X Lion: pari fails self tests
--------------------------+-------------------------------------------------
   Reporter:  jhpalmieri  |          Owner:  tbd                 
       Type:  defect      |         Status:  needs_review        
   Priority:  major       |      Milestone:  sage-5.0            
  Component:  packages    |       Keywords:  pari darwin lion osx
Work_issues:              |       Upstream:  N/A                 
   Reviewer:              |         Author:                      
     Merged:              |   Dependencies:                      
--------------------------+-------------------------------------------------
Changes (by jhpalmieri):

  * status:  new => needs_review


Old description:

> On OS X Lion, if you set SAGE_CHECK=yes and build pari, some tests fail.
> See
>
>   [http://sage.math.washington.edu/home/palmieri/misc/pari-2.5.0.p3.log]
>
> for a log file.

New description:

 On OS X Lion, if you set SAGE_CHECK=yes and build pari, some tests fail.
 See

   [http://sage.math.washington.edu/home/palmieri/misc/pari-2.5.0.p3.log]

 for a log file.

 ----

 New spkg:
 [http://sage.math.washington.edu/home/palmieri/SPKG/pari-2.5.1.p0.spkg]

--

Comment:

 Okay, nailed it.  On OS X Lion, 'gcc' is a symbolic link to '/usr/bin
 /llvm-gcc-4.2', but '/usr/bin/gcc-4.2' is a plain version of gcc.  So if,
 when building Pari, we do `export CC=gcc-4.2`, then self-tests pass when
 building with standard (`-O3`) optimization.  So we have an easy solution,
 but it leads to several questions:

  - Is the version of OS X (Lion vs. Snow Leopard) important, or is it only
 the version of XCode?  That is, should we just test whether 'LLVM' is in
 the output from `gcc --version` (or perhaps something more refined, like
 'LLVM' is in the output from `gcc --version` and gcc is version 4.2.1, or
 `gcc --version` contains the string "LLVM build 2.335.15.00")?

  - Should we make this change only for Pari, or should we do this when
 building all of Sage?  I have a feeling we do it on a case-by-case basis,
 since I think that not all spkgs respect the CC variable.  I tried it with
 cvxopt (see #12011), and it didn't seem to help, but it's worth exploring
 more...

 I've posted an spkg which tests whether we're using an 'LLVM' version of
 gcc 4.2.1.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12315#comment:12>
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