Hi, > I have toyed with singular-3.1.2 and tried to see if it could work with > sage.
nice, I meant to get around to it but never did. > The short story is that we should stay clear of it for a some time. > The singular executables are fine, the problems are with libsingular. > The headers shipped for libsingular are currently completely broken, > this is because they are working on their new build system and it has > growing pains. Did you report your findings upstream? [libsingular-devel] is probably the best place for this. We have a pretty good relationship with the Singular project, they usually respond to our problems really really quickly with a fix! > Once I fixed the headers with a few massive sed command I tried > to compile sage against it.... So far g++ has either hung or broke > in the process: > i686-pc-linux-gnu-g++ -pthread -O2 -march=native -fomit-frame-pointer -pipe > - fno-strict-aliasing -fno-strict-aliasing -DNDEBUG -fPIC - > I/usr/include/singular -I/usr/include -I/usr/include/csage -Isage/ext - > I/usr/include/python2.6 -c sage/libs/singular/function.cpp -o > build/temp.linux-i686-2.6/sage/libs/singular/function.o > error: command 'i686-pc-linux-gnu-g++' failed with exit status 1 > > This may not look like your usual log because it was done with > sage-on-gentoo where it is far easier for me to experiment with upgrading > individual parts of sage. gcc used is 4.4.5. Cheers, Martin -- name: Martin Albrecht _pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99 _otr: 47F43D1A 5D68C36F 468BAEBA 640E8856 D7951CCF _www: http://martinralbrecht.wordpress.com/ _jab: martinralbre...@jabber.ccc.de -- 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
