Making every 3rd party author adhere to the standard usage of CC/CXX is a bit like herding cats. It would be the cleanest fix to patch all the different build systems, sure. But wouldn't it be easier if Sage would set up its own gcc wrapper in $SAGE_LOCAL/bin? The first step of the Sage build process would then be to determine which architecture and compiler one wants to use set up the wrapper accordingly. Then you needn't have every spkg kludge around OSX 64bit brokenness, make sure that it calls the right linker on Solaris, ...
On Oct 28, 4:51 am, "Dr. David Kirkby" <[email protected]> wrote: > The fact Sage does not reliably respect the CC and CXX variables is a pain if > you want to use a non-GNU compiler, but I just found it causes problems on > openSUSE too. There g++ installs as /usr/bin/g++-4.5, not as 'g++'. So I've > got > to create a link. Note a difficult task, but it would be much better if Sage > would consistently respect CC and CXX. > > Dave -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
