#12954: Make MPIR support SAGE_FAT_BINARY on all systems
----------------------------------+-----------------------------------------
       Reporter:  vbraun          |         Owner:  tbd       
           Type:  defect          |        Status:  needs_work
       Priority:  blocker         |     Milestone:  sage-5.0.1
      Component:  packages        |    Resolution:            
       Keywords:                  |   Work issues:            
Report Upstream:  N/A             |     Reviewers:            
        Authors:  Jeroen Demeyer  |     Merged in:            
   Dependencies:                  |      Stopgaps:            
----------------------------------+-----------------------------------------

Comment (by leif):

 Replying to [comment:11 vbraun]:
 > `SAGE_FAT_BINARY` should be synonymous with `SAGE_GENERIC_BINARY`,
 though for historical reasons it isn't named well. From
 http://www.sagemath.org/doc/installation/source.html:
 >
 > SAGE_FAT_BINARY - to prepare a binary distribution that will run on the
 widest range of target machines, set this variable to "yes"

 That description is certainly insufficient (or, to be more precise, one
 shouldn't read it from right to left).  One should in general not prepare
 "fat" binaries on relatively new (e.g. Core i7) CPUs -- unless one knows
 what one's doing... ;-)

 IMHO the main purpose of `SAGE_FAT_BINARY` is to avoid the use of
 processor-specific ("hand-written") ''assembly code'' (and prevent Sage
 from using things like `-march=native`); it's still up to the
 ''distributor'' to make sure the compiler is targeted to the ''desired''
 CPU family (whichever that is).

 [[BR]]

 Doing some "sanity check" upon `sage -bdist` isn't all bad, but of course
 heavily depends on what (limited) architecture a specific binary
 distribution is supposed to be run on.


 ----

 I never liked `MPIR_EXTRA_OPTS` (for additional options to be passed to
 MPIR's `configure`), but it's named like this for consistency with other
 spkgs, i.e., historical reasons.  A couple of spkgs (or every spkg that
 supports such) use `${PKG_NAME}_EXTRA_OPTS`.

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