Dr. David Kirkby wrote: > > I tried it, but simply hard-coding the flag in custom.py (no checking what > compiler it is). It still fails to build, though the previous error message > has > gone, there are still other error messages. See below. > > Not knowing C++, I can't really comment on this. > > One thing I did note, is that if library=stlport4 is added as an option in > one > file, then it needs to be done in them all. So clearly this is something that > needs to be set globally as a CFLAG, and not implemented just in PolyBoRi. > > Dave
The compiler option -library=stlport4 should obviously go as a CXXFLAG, not a CFLAG. The couple of scripts I wrote on this ticket, http://trac.sagemath.org/sage_trac/ticket/7505 which needs reviewing, determine the C and C++ compilers based purely on what macros are defined. The script will return one of the following, to indicate the C compiler and C++ compilers (there are scipts called testcc.sh and testcxx.sh - one for C, the other C++) GCC - For gcc or a gcc-like C compiler on any platform Sun_Studio - For Sun Studio or earlier Sun C compiler HP_on_Tru64 - For a C compiler produced by HP/Compaq for Tru64 HP_on_HP-UX - For a C compiler produced by HP/Compaq for HP-UX IBM_on_AIX - For a C compiler produced by IBM for AIX HP_on_Alpha_Linux - For a C compiler produced by HP for Alpha linux (This script has not been tested on Alpha Linux, but is based on HP's documentation) Unknown - If the C compiler type is unknown Implementing something like this for Fortran is nowhere near as easy. 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
