Hello, David! Thanks for your reply, it was very useful.
You wrote 10 июля 2010 г., 1:47:31: > 1) It does not work on Solaris 10 on SPARC - see below. I suspect > there are some GNU-specific linker options, which will fail if the > Sun linker is used on Solaris 10. Looks like it is actually the case. > However ALGLIB, is not respecting the SAGE64 variable, so despite > SAGE64 being set to "yes", only a 32-bit binary was made. (This was > on a Sun Ultra 27, with a Xeon processor running OpenSolaris > 06/2009.) OK, will fix it. But I've though that you just add corresponding options to CFLAGS automatically. > Note also, Sage usually puts shared libraries in $SAGE_LOCAL/lib and > does not create directories like "alblib-bin" off of $SAGE_LOCAL. OK, will fix it too. Now I see that separate directory is in fact unnecessary. > I was impressed you had put the spkg-check file. As you can see, it > does pass all tests. On my Sun Ultra 27, it takes 8.2 seconds to > install, and 2 minutes and 1 second to both install and run the test > suite. Good. Is it OK for SAGE to have spkg which takes 2 minutes to test? Just don't know what are the timing requirements. You have a lot of packages, and testing ALL of them will take a lot of time. > I think it would be better if the test suite gave some feedback > after each test, rather than just at the end. Actually, it prints results line by line. I think that the reason is lack of flush() calls; it worked on Window and Linux, but different systems (and even different distros) may have different output buffering strategies. I'll to fix it. -- With best regards, Sergey mailto:sergey.bochka...@alglib.net -- 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
