On Sun, 28 Jan 2007 14:12:46 -0800, Justin C. Walker <[EMAIL PROTECTED]> wrote:
>> Hello,
>>
>> I have released SAGE-2.0. Enjoy!!
>
> That was a fast trip to 2.0! Congratulations on a lot of hard work
> successfully completed!
>
> A quick question:
>
> On my MacBook Pro, installation from scratch completed without a
> hitch, but at the very end, I got the line
>
> SAGE build/upgrade complete!
>
> and no shell prompt (I had typed 'make'). I eventually tired of
> waiting for completion, and interrupted (^C), and got
>
> ^Cmake: *** [all] Error 130
>
> Is this expected?
No. I have no clue why that would happen. I've built from scratch
many times on my MBP without ever seeing that problem, as have several
other people...
> Also, there is a 'sage-cleaner' process hanging around, owned by
> 'init'. It was started up during the build.
Yes, finally sage has a good way to:
(1) clean up tmp files it leaves around
(2) kill processes it spawns
and that is "sage-cleaner", which is a single lightweight process
that does 1 and 2. It should, however, terminate automatically
once there are no running SAGE processes on your system.
William
--~--~---------~--~----~------------~-------~--~----~
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
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~----------~----~----~----~------~----~------~--~---
