I noticed a couple of issues with polybori-0.5rc.p8 on Solaris. Note how on the first line, polybori uses the GNU C compiler gcc to compile a C file, but passes an unreconised option '-KPIC'. (That option would be acceptable to the Sun compiler).
Then on the very next line, it calls the Sun C++ compiler 'CC' to compile a .cc file! It sure gets in a mess! gcc -o Cudd/epd/so_epd.o -c -std=c99 -O3 -Wno-long-long -Wreturn-type -g -fPIC -KPIC -DNDEBUG -DPACKED -DHAVE_M4RI -DHAVE_IEEE_754 -DBSD -I/rootpool2/local/kirkby/sage-4.1.rc1/spkg/build/polybori-0.5rc.p8/src/boost_1_34_1.cropped -I/rootpool2/local/kirkby/sage-4.1.rc1/local/include/python2.6 -Ipolybori/include -ICudd/obj -ICudd/util -ICudd/cudd -ICudd/mtr -ICudd/st -ICudd/epd Cudd/epd/epd.c gcc: unrecognized option '-KPIC' /opt/SUNWspro/bin/CC -o polybori/src/so_BoolePolyRing.o -c -O3 -Wno-long-long -Wreturn-type -g -fPIC -ftemplate-depth-100 -g -fPIC -KPIC -O3 -Wno-long-long -Wreturn-type -g -fPIC -KPIC -DNDEBUG -DPACKED -DHAVE_M4RI -DHAVE_IEEE_754 -DBSD -I/rootpool2/local/kirkby/sage-4.1.rc1/spkg/build/polybori-0.5rc.p8/src/boost_1_34_1.cropped -I/rootpool2/local/kirkby/sage-4.1.rc1/local/include/python2.6 -Ipolybori/include -ICudd/obj -ICudd/util -ICudd/cudd -ICudd/mtr -ICudd/st -ICudd/epd polybori/src/BoolePolyRing.cc When I type $ ./sage -sh $ env I see: SAGE_ROOT=/rootpool2/local/kirkby/sage-4.1.rc1 PYTHONHOME=/rootpool2/local/kirkby/sage-4.1.rc1/local SAGE_PACKAGES=/rootpool2/local/kirkby/sage-4.1.rc1/spkg CP=cp LN=ln CXX=g++ So given CXX is defined as g++, it's not clear why polybori should use Sun's 'CC' as the C++ compiler. For what it is worth, after changing to gcc 4.2.4, I can get the following to build on 't2' --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
