Hi David, hi Franco,
currently Sage has a known weakness with the Maxima synchronization resp. the lisp processes that are started by Maxima, which hits only sporadically and seems to be related to dynamical memory allocation done deep in the bowels of the lisp implementation. It has never been really tracked down so far, but maybe Intrepid Ibex brings some gcc compiler version / glibc version / malloc version / linux kernel / whatsoever that triggers the problematic behaviour more often than in the past. Of course, this is wild guessing ... Michael had hoped that this would go away by switching to another lisp package, but I don't know what the state of matters is. I can also trigger this (or some completely different?) sporadic problem on my bronze-age 768 MByte 550 MHz PPC Mac PowerBook, but even building Sage takes more than half a day. I'll give Sage3.2.alpha3 a try there. Cheers, gsw --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
