Thanks, William! Unfortunately, this did not solve the issue. I am still getting the message "TypeError: Unable to start maxima".
Stan William Stein wrote: > On Fri, Nov 20, 2009 at 1:58 AM, Stan Schymanski <[email protected]> wrote: > >> Did the upgrade still work for you? >> Mine ended normally, but if I start the notebook and want to do >> something, I get the message that maxima could not be started. I'll have >> to compile from source (again). >> > > Try forcing rebuilding of the maxima spkg. > > sage -f maxima-5.19.1.p0 > > William > > > >> Cheers >> Stan >> >> Minh Nguyen wrote: >> >>> Hi Stan, >>> >>> On Thu, Nov 19, 2009 at 9:31 PM, Stan Schymanski <[email protected]> wrote: >>> >>> >>>> Dear all, >>>> >>>> I compiled sage 4.2 from source on my Macbook Pro with OSX 10.4.11 and >>>> when I tried sage -upgrade, I was asked to enter a commit message. I >>>> aborted (by typing :q) and the upgrade is continuing now, but this >>>> does not seem normal. Did anyone else experience something similar? >>>> >>>> >>> Yes. I was asked to enter a commit message because the README file has >>> changed. I suspect that the executable bits have changed. The README >>> file should have no executable bits. >>> >>> >>> >> -- >> To post to this group, send email to [email protected] >> To unsubscribe from this group, send email to >> [email protected] >> For more options, visit this group at >> http://groups.google.com/group/sage-support >> URL: http://www.sagemath.org >> > > > > -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
