#3761: [with patch; positive review] warning when run sage binary if the 
processor
instruction set doesn't support everything that was on the machine where
sage was built
---------------------+------------------------------------------------------
 Reporter:  was      |        Owner:  cwitty  
     Type:  defect   |       Status:  new     
 Priority:  blocker  |    Milestone:  sage-3.2
Component:  misc     |   Resolution:          
 Keywords:           |  
---------------------+------------------------------------------------------
Changes (by GeorgSWeber):

  * summary:  [with patch; needs review for an epsilon] warning when run
              sage binary if the processor instruction set
              doesn't support everything that was on the
              machine where sage was built => [with patch;
              positive review] warning when run sage binary
              if the processor instruction set doesn't
              support everything that was on the machine
              where sage was built

Comment:

 OK, I'm fine with he redefinition of "epsilon" to mean
 "sage-4515-sage_c_bug.patch".

 Since I just gave the entire #4515 a positive review, next try:

 Positive review for this ticket (Wiliams two patches) pending the prior
 inclusion of #4515.

 @William: I couldn't possibly make it to Loria (nice photos of you all, by
 the way!), but I surely do intend to attend some SD xy. Anyway, hope to
 see you again!

 Cheers, gsw

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/3761#comment:25>
Sage <http://sagemath.org/>
Sage - Open Source Mathematical Software: Building the Car Instead of 
Reinventing the Wheel
--~--~---------~--~----~------------~-------~--~----~
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