#13706: atlas spkg does not take the SAGE_ATLAS_ARCH variable into account when
SAGE_FAT_BINARY is set to 'yes'
------------------------------------------------------------------+---------
       Reporter:  tmonteil                                        |         
Owner:  GeorgSWeber                   
           Type:  defect                                          |        
Status:  positive_review               
       Priority:  major                                           |     
Milestone:  sage-duplicate/invalid/wontfix
      Component:  build                                           |    
Resolution:                                
       Keywords:  atlas, days43 denigration community management  |   Work 
issues:                                
Report Upstream:  N/A                                             |     
Reviewers:  Volker Braun                  
        Authors:                                                  |     Merged 
in:                                
   Dependencies:                                                  |      
Stopgaps:                                
------------------------------------------------------------------+---------

Comment (by jdemeyer):

 Replying to [comment:8 tmonteil]:
 > - "You either want a binary that runs on all reasonably old hardware for
 distribution, or you want to specify the architecture in detail" -> i want
 both, that is why local and global variables are made for !

 I don't understand what "both" could possibly mean. How can it run on all
 architectures while still being optimized for one architecture? If it
 needs to run on all architectures, it cannot use Core2-specific
 instructions for example, so how could be optimized for Core2?

 > Currently, if i want to tune atlas for a specific old architecture, and
 at the same time tell other packages not to use too recent sets of
 instructions (which is coherent), i simply can not.
 1) If the "specific old architecture" is the one you're building on, it's
 easy: don't set any environment variable and build as usual.

 2) If the "specific old architecture" is ''not'' the one you're building
 on but you still don't want a generic binary: first of all, why would you
 want that? But this can probably be achieved by setting specific `CFLAGS`,
 although this isn't really supported.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13706#comment:11>
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 unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to