#10572: compiler/binutils wrapper
---------------------------------------------------+------------------------
Reporter: vbraun | Owner:
GeorgSWeber
Type: enhancement | Status:
needs_review
Priority: major | Milestone: sage-5.10
Component: build | Resolution:
Keywords: compiler gcc wrapper rpath spkg | Work issues:
Report Upstream: N/A | Reviewers:
Authors: Volker Braun | Merged in:
Dependencies: | Stopgaps:
---------------------------------------------------+------------------------
Comment (by vbraun):
Its true that gcc won't build itself with the wrapper, but then we build
gcc right at the beginning before we build any troublesome libraries. And
the first stage doesn't need optimizations, to even moderately broken
compilers should be fine.
We definitely should think about using a special case from an already
existing environment variable to avoid creating too many obscure
configuration options that we can never actually test. JP wants a setting
so that he can play with potentially broken compilers, and setting
`SAGE_INSTALL_GCC=no` is what you logically would want to set in this use
case.
The basic fact is that only one program can be installed as
`$SAGE_LOCAL/bin/gcc` So you don't have 4 independent choices of sage-gcc
yes/no and compilerwrapper yes/no.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10572#comment:55>
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
