#12751: Sage fails to build with GCC-4.7.0
-----------------------------------+----------------------------------------
Reporter: mariah | Owner: GeorgSWeber
Type: defect | Status: new
Priority: critical | Milestone: sage-5.0
Component: build | Resolution:
Keywords: GCC 4.7.0 C++11 | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: | Stopgaps:
-----------------------------------+----------------------------------------
Comment (by leif):
Replying to [comment:5 leif]:
> !SciPy's test suite fails to build due to an internal compiler error.
Turns out that this isn't reproducible. Actually, in the first attempt
(although with `SAGE_CHECK=yes`) ''the build'' failed, before the test
suite got built or run.
I've then successfully rebuilt !SciPy without `SAGE_CHECK=yes`, and now
also again with it.
Nevertheless, !SciPy's `spkg-check` (for whatever reason a Python script)
is suboptimal, and `spkg-install` '''overwrites''' `LDFLAGS`. (It also
unsets `CFLAGS` etc., but distutils take these from Python, so that's not
as bad as it sounds, provided one doesn't want to rebuild [Python and]
!SciPy with different flags.)
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12751#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 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.
