I'm copying this to Steven Knight, a SCons developer, since he might have some comments.
When building Sage 4.1.1.alpha0 on my home machine, which does not have the Sun Studio Compiler suite installed, the Sage package containing the 'modified Sage library' builds ok. (I eventually get failures at ecl, but that is another issue). On the machine 't2' the 'modified Sage library' fails. For some reason, despite gcc having been used to compile the C files, Sun's /opt/SUNWspro/bin/CC gets used for the C++ files. The Sun compiler is unhappy about the C++ code and exits with an error. (PolyBoRi had the same issue, but Alexander Dreyer fixed that) However, that aside, the call to Sun's compiler is mixing up GNU and Sun flags, which they are I believe being inherited from SCons. Perhaps SCons is giving the wrong flags, or perhaps somewhere in the Sage code some GNU flags are added. But either way, the result is wrong. /opt/SUNWspro/bin/CC -o src/so_ZZ_pylong.o -c -KPIC -fPIC -I/rootpool2/local/kirkby/sage-4.1.1.alpha0/local/include -I/rootpool2/local/kirkby/sage-4.1.1.alpha0/local/include/python2.6 -I/rootpool2/local/kirkby/sage-4.1.1.alpha0/local/include/NTL -Iinclude src/ZZ_pylong.cpp CC: Warning: Option -fPIC passed to ld, if ld is invoked, ignored otherwise "src/ZZ_pylong.cpp", line 47: Error: "ZZ_set_pylong(NTL::ZZ&, _object*)" is expected to return a value. 1 Error(s) detected. Note -KPIC is an acceptable flag to Sun's compiler, but -fPIC is not. (The converse is true with gcc). I've created this as bug id http://sagetrac.org/sage_trac/ticket/6595 Dave --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
