#14429: Singular omalloc requires 8-byte alignment on SPARC
-------------------------------------------------------+--------------------
       Reporter:  jdemeyer                             |         Owner:  
drkirkby       
           Type:  defect                               |        Status:  
positive_review
       Priority:  major                                |     Milestone:  
sage-5.9       
      Component:  porting: Solaris                     |    Resolution:         
        
       Keywords:  SPARC alignment SIGBUS omalloc       |   Work issues:         
        
Report Upstream:  Reported upstream. No feedback yet.  |     Reviewers:  Volker 
Braun   
        Authors:  Jeroen Demeyer                       |     Merged in:         
        
   Dependencies:                                       |      Stopgaps:         
        
-------------------------------------------------------+--------------------

Comment (by jpflori):

 FYI, from the errors I had reported at:
 * https://groups.google.com/d/msg/sage-devel/DhJcPuFIlPo/ToQuuJzu_BMJ
 except for the ones fixed by #13151, this fixes the error in
 * sage/crypto/mq/sr.py
 although I still get an error in
 * devel/sage/sage/interfaces/expect.py
 {{{
 sage -t devel/sage/sage/interfaces/expect.py
 **********************************************************************
 File "devel/sage/sage/interfaces/expect.py", line 1089, in
 sage.interfaces.expec
 t.Expect._crash_msg
 Failed example:
     singular('2+3')
 Exception raised:
     Traceback (most recent call last):
       File
 "/infres/post/flori/sage-5.9.beta3-infres2/local/lib/python2.7/site-p
 ackages/sage/doctest/forker.py", line 460, in _run
         self.execute(example, compiled, test.globs)
       File
 "/infres/post/flori/sage-5.9.beta3-infres2/local/lib/python2.7/site-p
 ackages/sage/doctest/forker.py", line 819, in execute
         exec compiled in globs
       File "<doctest sage.interfaces.expect.Expect._crash_msg[4]>", line
 1, in <
 module>
         singular('2+3')
       File
 "/infres/post/flori/sage-5.9.beta3-infres2/local/lib/python2.7/site-p
 ackages/sage/interfaces/singular.py", line 724, in __call__
         return SingularElement(self, type, x, False)
       File
 "/infres/post/flori/sage-5.9.beta3-infres2/local/lib/python2.7/site-p
 ackages/sage/interfaces/singular.py", line 1184, in __init__
         self._name = parent._create( value, type)
       File
 "/infres/post/flori/sage-5.9.beta3-infres2/local/lib/python2.7/site-p
 ackages/sage/interfaces/singular.py", line 685, in _create
         self.set(type, name, value)
       File
 "/infres/post/flori/sage-5.9.beta3-infres2/local/lib/python2.7/site-p
 ackages/sage/interfaces/singular.py", line 628, in set
         raise TypeError, msg
     TypeError: [Errno 22] Invalid argument
     Error evaluating def sage51=2+3; in Singular
 **********************************************************************
 File "devel/sage/sage/interfaces/expect.py", line 1114, in
 sage.interfaces.expec
 t.Expect._synchronize
 Failed example:
     R.<x> = QQ[]; f = x^3 + x + 1;  g = x^3 - x - 1; r = f.resultant(g);
 gap(ZZ)
 ; singular(R)
 Expected:
     Integers
     //   characteristic : 0
     //   number of vars : 1
     //        block   1 : ordering lp
     //                  : names    x
     //        block   2 : ordering C
 Got:
     Integers
     Singular crashed -- automatically restarting.
     //   characteristic : 0
     //   number of vars : 1
     //        block   1 : ordering lp
     //                  : names    x
     //        block   2 : ordering C
 **********************************************************************
 2 items had failures:
    1 of   6 in sage.interfaces.expect.Expect._crash_msg
    1 of   3 in sage.interfaces.expect.Expect._synchronize
     [81 tests, 2 failures, 26.3 s]
 ----------------------------------------------------------------------
 sage -t devel/sage/sage/interfaces/expect.py  # 2 doctests failed
 ----------------------------------------------------------------------
 Total time for all tests: 27.1 seconds
     cpu time: 3.7 seconds
     cumulative wall time: 26.3 seconds
 }}}
 Note that running singular('2+3') in sage works fine and so does the
 second problematic doctest.
 I still get the numerical noise problem from
 * sage/rings/polynomial/polynomial_element.pyx
 which is undoubtly unrelated,
 and bunches of timeouts, but now I even get those on quite powerfull and
 recent computers...

 Oh and I still had troubles building singular because of C++ headers the
 system has in /usr/local/include which seem incompatible with the ones
 Sage's GCC ships, and this path is added by Singular in
 src/Singular/Makefile[.in] to CPPFLAGS if gcc version is greater than 4.
 You could argue that it is the computer install itself which is ill-
 configured, but when removing the -I/usr/local/include from
 Singular/Makefile[.in], everything builds fine.
 I've opened a ticket upstream but thanks to Singular serving their http
 server on a unusual port, i cannot access it at the moment.

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