On May 8, 7:14 pm, "John Cremona" <[EMAIL PROTECTED]> wrote:
> 2008/5/8 mabshoff <[EMAIL PROTECTED]>:
<SNIP>
> > Yes, I wouldn't use "bizarre" but "buggy and broken", but thanks for
> > testing and feedback :).
>
> You're welcome. It is certainly possible I got confused doing all
> that. Also the machine I was doing it on has a habit of disconnecting
> me when idle, so I have to reconnect, and then might forget to reset
> the enronment variables.
Ok, that would explain a couple of the oddities you obseve.
> Question: at what point is it important to have SAGE_PBUILD and
> SAGE_BUILD_THREADS set? Is it only when Sage is first built from
> source, or should they be set for other things (sage -br and sage
> -clone, for example)? If the latter then it is highly likely that
> they were *not* set after the initial build (becuase of being
> disconnected as I said) which would mean that some of those timings
> are not trustworthy.
You should set them before building Sage and then every time you
invoke "sage -b, clone & friends". If you switch back and forth build
and clone times will be odd, i.e. if you clone a branch build with the
old build system under pbuild the forced rebuild will happen. This
will be a non-issue once we make pbuild default and eventually
deprecate the old setup.py based build.
> John
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
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-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
