Minh Nguyen wrote: > Hi David, > > On Fri, Jul 17, 2009 at 9:15 AM, Dr. David > Kirkby<david.kir...@onetel.net> wrote: > > <SNIP> > >> As a quick hack, I have managed to build polybori. I've done that by >> ensuring that the Sun tools are no longer in the path, as there are no >> longer any links to the Sun tools to /usr/bin. Apparently when Sun >> Studio is installed, one can deselect the option of having the links >> created, although this is the default. >> >> So Minh's build of Sage should go past the polybori obstacle now. > > So is there an updated spkg of PolyBori that I can use? Or can I just > continue using the one I uploaded to build on t2?
Hi Minh, The package I made at http://sage.math.washington.edu/home/kirkby/Solaris-fixes/polybori/polybori-0.5rc.p9.spkg which fixes the linker flags, should build on t2 now the Sun compiler tools are not in the usual path, though I suspect it might need a completely fresh build, since polybori inherits variables from SCons, which no doubt get them from elsewhere. I have built polybori both on by my home computer and t2 using gcc 4.4.0. There are however lots of warnings. scons: done building targets. Done installing PolyBoRi. Removing dynamic libraries... Done removing dynamic libraries. real 17m24.084s user 15m34.903s sys 1m35.298s Successfully installed polybori-0.5rc.p9 Now cleaning up tmp files. To get around the MPIR problem on 't2', I've changed the default version of gcc on 't2' from 4.4.0 to 4.2.4. Since doing that, it would appear polybori is failing to build on 't2', but there might be some other reason. So certainly testing http://sage.math.washington.edu/home/kirkby/Solaris-fixes/polybori/polybori-0.5rc.p9.spkg on 't2' with the default compiler (gcc 4.2.4) would be useful. Even if 4.2.4 refuses to compile polybori, I can apply a fix to sort the MPIR issue out and use gcc 4.4.0. So we can definitely get past the MPIR and polybori issues on t2. But clearly polybori has a few issues which need to be resolved. I've managed to get to the same point on both t2 and my home machine before the build fails. This looks to me like this is code written for the Sage project, not an included program. As the error is: "sage: There was an error installing modified sage library code." So someone can hopefully see why it fails. warning: /export/home/drkirkby/sage/sage-4.1/devel/sage-main/sage/symbolic/../li bs/ginac/decl.pxi:113:33: Function signature does not match previous declaration warning: /export/home/drkirkby/sage/sage-4.1/devel/sage-main/sage/symbolic/../li bs/ginac/decl.pxi:114:29: Function signature does not match previous declaration warning: /export/home/drkirkby/sage/sage-4.1/devel/sage-main/sage/symbolic/../li bs/ginac/decl.pxi:115:18: Function signature does not match previous declaration warning: /export/home/drkirkby/sage/sage-4.1/devel/sage-main/sage/symbolic/../li bs/ginac/decl.pxi:342:60: Function signature does not match previous declaration Updating Cython code.... Building modified file sage/symbolic/constants_c.pyx. python `which cython` --embed-positions --incref-local-binop -I/export/home/drki rkby/sage/sage-4.1/devel/sage-main -o sage/symbolic/constants_c.cpp sage/symboli c/constants_c.pyx sage/symbolic/constants_c.pyx --> /export/home/drkirkby/sage/sage-4.1/local//lib /python/site-packages//sage/symbolic/constants_c.pyx Time to execute 1 commands: 2.56958293915 seconds Finished compiling Cython code (time = 4.12907505035 seconds) running install running build running build_py copying sage/symbolic/constants.py -> build/lib.solaris-2.10-sun4u-2.6/sage/symb olic running build_ext building 'sage.ext.fast_callable' extension creating build/temp.solaris-2.10-sun4u-2.6/sage/ext gcc -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/export/home/drkirkby/sage/sage-4.1/local//include -I/export/home/drkirkby/sa ge/sage-4.1/local//include/csage -I/export/home/drkirkby/sage/sage-4.1/devel//sa ge/sage/ext -I/export/home/drkirkby/sage/sage-4.1/local/include/python2.6 -c sag e/ext/fast_callable.c -o build/temp.solaris-2.10-sun4u-2.6/sage/ext/fast_callabl e.o -w In file included from sage/ext/fast_callable.c:141: /export/home/drkirkby/sage/sage-4.1/local//include/pari/paripriv.h:258: error: e xpected ';', ',' or ')' before numeric constant /export/home/drkirkby/sage/sage-4.1/local//include/pari/paripriv.h:259: error: e xpected ';', ',' or ')' before numeric constant In file included from sage/ext/fast_callable.c:141: /export/home/drkirkby/sage/sage-4.1/local//include/pari/paripriv.h:428: error: e xpected identifier before numeric constant error: command 'gcc' failed with exit status 1 sage: There was an error installing modified sage library code. real 0m20.396s user 0m16.369s sys 0m3.463s Error building new version of SAGE. You might try typing 'sage -ba' or write to sage-support with as much informatio n as possible. real 0m44.635s user 0m34.581s sys 0m8.624s sage: An error occurred while installing sage-4.1 --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
