#12830: Improve handling of CFLAGS in GMP-ECM's spkg-install
----------------------------------------------------------------------------------------------------+
       Reporter:  leif                                                          
                    |         Owner:  leif        
           Type:  enhancement                                                   
                    |        Status:  needs_review
       Priority:  major                                                         
                    |     Milestone:  sage-5.0    
      Component:  packages                                                      
                    |    Resolution:              
       Keywords:  spkg -march=native assembler error Darwin MacOS __GMP_CFLAGS 
__MPIR_CFLAGS gmp.h  |   Work issues:              
Report Upstream:  N/A                                                           
                    |     Reviewers:              
        Authors:  Leif Leonhardy                                                
                    |     Merged in:              
   Dependencies:                                                                
                    |      Stopgaps:              
----------------------------------------------------------------------------------------------------+

Comment (by leif):

 Replying to [comment:2 jdemeyer]:
 > Instead of copying all this complicated "detect CFLAGS from MPIR" stuff,
 I propose the following: make the MPIR spkg store its $CC and $CFLAGS
 somewhere (say, in $SAGE_LOCAL/etc/mpirflags) and read that?  That would
 replace the horrible kludge we have now in this ecm spkg.

 Well, using `gmp.h` is the documented, supposed way to do this, and
 compatible to GMP.

 Extracting the flags isn't complicated (nor a kludge); complain to the
 MPIR developers that they break GMP compatibility even with `--enable-
 gmpcompat` (as I already did).  The extra code working around this is six
 lines IIRC, and not really complicated.

 [[BR]]

 If you want MPIR and GMP to store the flags elsewhere, suggest them to
 create a `pkg-config` file (although "standard" `.pc` files don't have a
 variable for the compiler used).

 We could of course create our own in MPIR's (and GMP's) `spkg-install`,
 but that doesn't make much sense to me, since then again our other spkgs
 using the `.pc` file would depend on Sage's versions (and a recent version
 of Sage itself).

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