On 2010-Oct-28 02:31:19 -0700, Volker Braun <[email protected]> wrote: >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, ...
For the FreeBSD port, I just create symlinks for g++, gcc, gfortran and make in $SAGE_LOCAL/bin - I felt this was the easiest way out of the hard-wired name morass. (The 'make' symlink is needed because 'make' on *BSD is pmake, not GNU make - which is installed as gmake). That just leaves problems with people assuming /bin/sh is bash (last I checked, there were still a few of these). -- Peter Jeremy
pgpmpMm2EhZME.pgp
Description: PGP signature
