#7095: os x 10.6 port -- numerous mysterious errors caused by weird "abort trap"
issue
-----------------------+----------------------------------------------------
   Reporter:  was      |       Owner:  tbd     
       Type:  defect   |      Status:  new     
   Priority:  blocker  |   Milestone:  sage-4.3
  Component:  porting  |    Keywords:          
Work_issues:           |      Author:          
   Upstream:  N/A      |    Reviewer:          
     Merged:           |  
-----------------------+----------------------------------------------------

Comment(by jhpalmieri):

 Replying to [comment:10 fwclarke]:
 > I wonder about lines 123--124 of local/lib/python/config/Makefile (which
 have been there since at least 3.1.4):
 > {{{
 > MACOSX_DEPLOYMENT_TARGET=10.3
 > export MACOSX_DEPLOYMENT_TARGET
 > }}}
 > It seems to be these lines that are giving rise (in 10.6 but not in
 10.5) to many warnings of the form
 > {{{
 > #warning Building for Intel with Mac OS X Deployment Target < 10.4 is
 invalid.
 > }}}
 > Whether this is causing the problems, I don't know, but it does need to
 be changed (presumably to 10.4).

 This message is fixed (it seems) in Python 2.6.4 -- we use 2.6.2 right
 now.  Updating to 2.6.4 doesn't help with the main problem here, though.

 Here are a few random comments which don't tell me much, but maybe they'll
 help someone else.  The failure in arith.py is a false positive: it is
 from the function {{{factorial}}}, but the doctest is actually calling
 {{{factorial}}} from functions/other.py.  If you preface the doctests in
 arith.py with something like {{{from sage.rings.arith import factorial}}},
 then doctests for that file pass.  Maybe this should be done anyway?

 Re the error in rings/polynomial/pbori.pyx: it's weird.  If I put in some
 print statements, then I find that the problem comes from the line
 {{{
         gb = groebner_basis(self.gens(), **kwds)
 }}}
 This calls the function {{{groebner_basis}}} in polybori.gbcore, which
 ends when it hits a massive "return" statement (in the nested function
 {{{call_algorithm}}}).  I can change that statement from
 {{{
 return  ...blah...
 }}}
 to
 {{{
 XX = ...blah...
 print XX
 return XX
 }}}
 and it successfully prints {{{XX}}}, but then it crashes.

 Re the error in plot/text.py: this one can be reproduced in pure Python as
 follows:
 {{{
 $ sage -python
 Python 2.6.2 (r262:71600, Dec 10 2009, 21:33:56)
 [GCC 4.2.1 (Apple Inc. build 5646) (dot 1)] on darwin
 Type "help", "copyright", "credits" or "license" for more information.
 >>> import matplotlib.pyplot as plt
 >>> plt.plot([1,2,3])
 [<matplotlib.lines.Line2D object at 0x101eb2490>]
 >>> plt.savefig('a.pdf')
 /Applications/sage/local/bin/sage-sage: line 356: 62648 Abort trap
 python "$@"
 }}}
 This seems interesting; does it help to have a failure coming from pure
 Python?

 Most of the others seem to call {{{bool}}} and perhaps are related to
 ginac?

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