#9703: Doctest failures caused by non-working sympow on 32-bit Solaris x86 and
32-bit OpenSolaris
----------------------------+-----------------------------------------------
   Reporter:  drkirkby      |       Owner:  GeorgSWeber                         
     
       Type:  defect        |      Status:  needs_review                        
     
   Priority:  major         |   Milestone:  sage-4.5.3                          
     
  Component:  build         |    Keywords:                                      
     
     Author:  David Kirkby  |    Upstream:  Reported upstream. Little or no 
feedback.
   Reviewer:                |      Merged:                                      
     
Work_issues:                |  
----------------------------+-----------------------------------------------

Comment(by jdemeyer):

 Replying to [comment:18 drkirkby]:
 > > You could use to check
 > >  * whether or not the patch needs to be applied
 > >  * whether the result is correct after possibly applying the patch (do
 this on all systems!)
 >
 > I don't personally feel there is a need to do this.
 >  * It makes use of gcc-specific options.
 It doesn't.  I just added those options to show how the behaviour changes.
 My idea would be to run testfpu.c without any options and check the
 result.

 >  * It was not done before, so I end up making further changes to a
 package which is already a complete mess.
 I believe that my program is a cleaner solution. For example, are you sure
 you don't need the patch on Darwin? Also, the following code looks very
 suspicious:
 {{{
 for machine_hardware in ix86 i386 i486 i586 i686 x86_64 i86pc ia64
 }}}

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