#20738: singular 3.1.7 fails to build using GCC 6
-------------------------------------+-------------------------------------
Reporter: aapitzsch | Owner:
Type: defect | Status: needs_review
Priority: major | Milestone: sage-7.3
Component: build | Resolution:
Keywords: GCC6 | Merged in:
Authors: André Apitzsch | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/aapitzsch/gcc6issue | 04c0af9477f794f5d00a1c813725049d340bf4bd
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by leif):
While this (or a similar patch I posted on sage-release) allows building
Singular with GCC 6.1 (and without `-std=c++98` or `-std=c++11`), the
resulting binaries crash for me (even when compiled with `-std=c++98`).
Seems we have to fiddle with optimization flags as well, which doesn't
necessarily mean it's GCC's fault.
IIRC, with `-O1` in `CPPFLAGS` (which aren't consistently used or get
overridden by other settings, just like `CXXFLAGS`), I obtained a version
(of Sage 7.2 btw.) where `./sage` and `./sage --singular` did no longer
segfault, but building the documentation still crashed...
(The previous segfaults happened immediately when initializing
libsingular, as also reported by someone else on sage-release, in a thread
for Sage 7.3.beta2 related to GCC 6.1 and BRiAl.)
--
Ticket URL: <https://trac.sagemath.org/ticket/20738#comment:6>
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 https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
