> Hi! > > This is related with #9583. > > If the patch from #1396 is applied, Sage segfaults on t2 at startup. > It seems that the offending part of the code is in sage/libs/singular/ > option.pyx. > > I thought that Cython generates C code, which is then processed > further with gcc. But in this case, it seems that C++ code is > generated. However, this C++ code is still processed with gcc, not g+ > +. This gives to rise to a compiler warning, and it might be the > reason for the segfault. > > Why is C++ generated (assuming that the file option.cpp is Cython- > generated)? Is it because option.pyx links against some code of > Singular? > > And why is gcc rather than g++ invoked? How can this be changed? > Hi,
c++ is requested in module_list.py. What compiles what is decided by distutils. I don't observe this problem but I don't know what #1396 is all about. Francois -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
