#18027: Move interrupts to Cython
-------------------------------------------------+-------------------------
       Reporter:  jdemeyer                       |        Owner:
           Type:  enhancement                    |       Status:  closed
       Priority:  major                          |    Milestone:  sage-6.6
      Component:  cython                         |   Resolution:  fixed
       Keywords:                                 |    Merged in:
        Authors:  Jeroen Demeyer                 |    Reviewers:  Jean-
Report Upstream:  Reported upstream. No          |  Pierre Flori
  feedback yet.                                  |  Work issues:
         Branch:                                 |       Commit:
  6d738d6e869b869ccaf68a5db6a166542647dd7d       |     Stopgaps:
   Dependencies:                                 |
-------------------------------------------------+-------------------------

Comment (by fbissey):

 I'll surely open a follow up ticket about that `build` directory question
 once I have figured out to deal with it. I am not completely sure you have
 totally broken all "global" sage install and whether or not making those
 install carry at least a fragment of the build folder will fix it
 properly.
 Who else needs to have their build folder kept?
 It joins a basket of issues that I have duct-taped in sage-on-gentoo for
 years to have doctest and spyx files to work properly. If I had spent more
 time on fixing the installation of sage headers and various auxiliary
 files rather than the duct tape we wouldn't be there today.

 That's a sample
 {{{
     1 item had failures:
        1 of   4 in sage.doctest.tests.sig_on
         [2 tests, 1 failure, ...]
     ----------------------------------------------------------------------
     sage -t --warn-long 0.0 sig_on.rst  # 1 doctest failed
     ----------------------------------------------------------------------
     ...
     1
 Got:
     Running doctests with ID 2015-05-24-22-01-48-66399ec6.
     Doctesting 1 file.
     sage -t --warn-long 0.0 sig_on.rst
     **********************************************************************
     File "sig_on.rst", line 3, in sage.doctest.tests.sig_on
     Failed example:
         cython('sig_on()')
     Exception raised:
         Traceback (most recent call last):
           File "/usr/lib64/python2.7/site-
 packages/sage/doctest/forker.py", line 496, in _run
             self.compile_and_execute(example, compiler, test.globs)
           File "/usr/lib64/python2.7/site-
 packages/sage/doctest/forker.py", line 858, in compile_and_execute
             exec(compiled, globs)
           File "<doctest sage.doctest.tests.sig_on[0]>", line 1, in
 <module>
             cython('sig_on()')
           File "sage/misc/cython_c.pyx", line 63, in
 sage.misc.cython_c.cython (build/cythonized/sage/misc/cython_c.c:949)
             sage.server.support.cython_import_all(tmpfile, globals(),
           File "/usr/lib64/python2.7/site-
 packages/sage/server/support.py", line 85, in cython_import_all
             create_local_c_file=create_local_c_file)
           File "/usr/lib64/python2.7/site-
 packages/sage/server/support.py", line 62, in cython_import
             **kwds)
           File "/usr/lib64/python2.7/site-packages/sage/misc/cython.py",
 line 519, in cython
             raise RuntimeError("Error compiling
 {}:\n{}\n{}".format(filename, log, err))
         RuntimeError: Error compiling /home/fbissey/.sage/temp/QCD-
 nzi3/10231/tmp_FdPxlK.spyx:
         running build
         running build_ext
         building
 '_home_fbissey__sage_temp_QCD_nzi3_10231_tmp_FdPxlK_spyx_0' extension
         creating build
         creating build/temp.linux-x86_64-2.7
         x86_64-pc-linux-gnu-gcc -pthread -fPIC -I/usr/include/csage
 -I/usr/include -I/usr/include/python2.7 -I/usr/lib/python/site-
 packages/numpy/core/include -I/usr/share/sage/src/sage/ext
 -I/usr/share/sage/src -I/usr/share/sage/src/sage/gsl
 -I/home/fbissey/.sage/temp/QCD-nzi3/10231 -I/usr/include/python2.7 -c
 _home_fbissey__sage_temp_QCD_nzi3_10231_tmp_FdPxlK_spyx_0.c -o build/temp
 .linux-
 x86_64-2.7/_home_fbissey__sage_temp_QCD_nzi3_10231_tmp_FdPxlK_spyx_0.o -w
 -O2
     <BLANKLINE>
         In file included from
 _home_fbissey__sage_temp_QCD_nzi3_10231_tmp_FdPxlK_spyx_0.c:248:0:
         /usr/share/sage/src/sage/ext/interrupt/pxi.h:7:63: fatal error:
 build/cythonized/sage/ext/interrupt/interrupt_api.h: No such file or
 directory
          #include "build/cythonized/sage/ext/interrupt/interrupt_api.h"
                                                                        ^
         compilation terminated.
         error: command 'x86_64-pc-linux-gnu-gcc' failed with exit status 1
     <BLANKLINE>
     **********************************************************************
     1 item had failures:
        1 of   4 in sage.doctest.tests.sig_on
         [2 tests, 1 failure, 0.86 s]
     ----------------------------------------------------------------------
     sage -t --warn-long 0.0 sig_on.rst  # 1 doctest failed
     ----------------------------------------------------------------------
     Total time for all tests: 0.9 seconds
         cpu time: 0.0 seconds
         cumulative wall time: 0.9 seconds
     1
 **********************************************************************
 1 item had failures:
    1 of  45 in sage.doctest.test
     [44 tests, 1 failure, 98.40 s]
 ----------------------------------------------------------------------
 sage -t --long /usr/share/sage/src/sage/doctest/test.py  # 1 doctest
 failed
 }}}

--
Ticket URL: <http://trac.sagemath.org/ticket/18027#comment:40>
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.
For more options, visit https://groups.google.com/d/optout.

Reply via email to