Until I downloaded 4.1.1.alpha0, every time there has been a failure of Sage on Solaris, there has been a useful error message.
Since downloading 4.1.1.alph0, I've found the install just dies for no known reason some times. (I've also seen the usual thing about running sage sh etc). The last time the install died was on t2, and the install.log looks like this: **************************************************** Starting build... Removing old PolyBoRi install... Done removing old PolyBoRi install. Running build_polybori... And there the install.log has stopped. Nothing. The make process has died. It's not only polybori this has happened to, but I think mpir and flint. Every time it's restarted, so it works ok. This has happened on both my Sun Blade 2000 and the Sun T5240 't2'. Is there anything which might have changed in this release that could be responsible for this? Once I could understand, but several times on two different machines seems a bit too much of a coincidence to me. Dave --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
