Dr. David Kirkby wrote:
Jaap Spies wrote:
Dr. David Kirkby wrote:
We know from recent discussions over sage-env and the hassles that
http://trac.sagemath.org/sage_trac/ticket/7818
caused, that setting CFLAGS, CXXFLAGS etc globally will cause a build
failure in Sage. It would therefore seem sensible that we exit with an
error message if someone sets CFLAGS when building Sage.
I think it is more sensible that the spkgs involved do an 'unset
CFLAGS', etc..
Laying the resposibilities were they belong.
A lot of spkgs will not built in 64 bit mode unless CFLAGS has a
sensible flag.
Jaap
I would normally agree with you, but think this could be risky.
Risky? What is wrong with cython unset CFLAGS?
I plea to put responsibilities where they belon.
Having had my fingers burnt once over setting CFLAGS globally, I would
avoid that at all costs. Which is why I wondered whether we should check
they are not set, to avoid any surprises later on.
Quite a few spkg-install are a simply: python setup.py install.
They fail on Open Solaris x64 if CFLAGS does not include -m64.
As I proposed the other day, which William liked, we set
SAGE_COMMON_CFLAGS
to a sensible set of compiler flags, suitable for most packages.
spkg-install then use
CFLAGS="SAGE_COMMON_CFLAGS"
export CFLAGS
That way, CFLAGS is not set globally, but any package can get a sensible
set if they choose to.
This may not be the most convenient approach, but it is the most risk-free.
Future music!
Jaap
Dave
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
