Thanks for the explanations! For my own build, I recovered by doing "sage -ba" as previously reported. So I don't know whether the original problem (running sage for the first time after an apparently successful build) was caused by the SAGE_PBUILD thing or not. Before doing "sage -ba" I also did export SAGE_PBUILD= which was intended to "switch off" this feature.
John 2008/5/2 mabshoff <[EMAIL PROTECTED]>: > > On May 1, 9:02 pm, "John Cremona" <[EMAIL PROTECTED]> wrote: > > Hi John, > > > > Thanks -- I mistakenly thought "pbuild" was short for "parallel build". > > Yes, it is meant to emphasize the parallel nature. Gary builds > routinely with 8 cores on his box and it cuts down the build time in a > linear fashion. > > > > If it is not about building Sage, while is it called SAGE_PBUILD? > > It is building the Sage library in parallel. I guess since I sat next > to Gary when the ideas where formulated by us it is so obvious to me > that I would never consider anything else. But I guess the problem is > that Sage is three things as William always points out in his talks. > > Gary wants to do build spkg in parallel, but I am more than skeptical > if that is worth it and doesn't open up a whole other can of worms. > That said I am sure we will have parallel spkg builds in less than six > months ;) > > > > Anyway, can someone remind me what causes this and how to fix it? > > wjp found the likely cause and Gary is posting a patch, so hopefully > it will all be sorted out in rc0. > > Cheers, > > Michael > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
