#9583: Unhandled SIGSEGV with 4.5.2.alpha0 on t2
-----------------------+----------------------------------------------------
Reporter: mpatel | Owner: drkirkby
Type: defect | Status: new
Priority: blocker | Milestone: sage-4.5.2
Component: solaris | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-----------------------+----------------------------------------------------
Comment(by SimonKing):
Replying to [comment:21 drkirkby]:
> Replying to [comment:19 jhpalmieri]:
> ...
> What is certainly not a good idea is that the '''C''' compiler gcc is
being invoked to compile a '''C++''' program. Since option.cpp is a C++
file, it should be compiled with g++, not gcc.
So, the crucial question is: Why is Cython generating a C++ file rather
than a C file?
Does it generate C++ since it is linked against Singular sources (which
ostensibly are C++)?
And what happens if one invokes g++ rather then gcc on the Cython-
generated code?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9583#comment:22>
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.
