On Fri, Jun 19, 2009 at 1:13 PM, gsw<georgswe...@googlemail.com> wrote:
>
>
>
> On 19 Jun., 08:50, Craig Citro <craigci...@gmail.com> wrote:
>> > Yes, the parallel build code was reworked for 4.0.1. Not sure why
>> > we're seeing this, but still.
>>
>> Well, the parallel build code in 4.0.1 *should* be contained to the
>> sage build itself (it's in sage's setup.py, and it's a separate
>> builder that one has to instantiate). I won't say it's impossible,
>> because I know I'd have to eat my words, but I think it's at least
>> pretty unlikely.
>>
>> That said, I think this is an issue with some race condition in our
>> build process. I don't have a 10.4.11 machine to look into this, and I
>> definitely don't want to before 4.0.2 (which is done) -- one can
>> simply unset MAKE and the problem goes away. ;)
>>
>
> Yeah, sure (except for the double time the build then needs ...). It's
> definitely not a blocker for 4.0.2, especially if it occurs only on OS
> X 10.4.11.
>
>> Georg, you should definitely file a ticket for this on trac ...
>> hopefully someone will start looking into it during the next release
>> cycle.
>
> I'll open a trac ticket and look myself a bit into this. It might take
> several releases until I get anywhere, however. I never looked at
> "parallel building" or the r.spkg / rpy.spkg before.
Here is everything to know about parallel building with Sage:
(1) some spkg's use
$MAKE
instead of
make
(2) packages for which we've had any known problems with parallel make
use "make".
(3) some packages for which parallel make works fine and for which
people thought to check (!) have $MAKE.
There's nothing else. In particular, multiple packages are not built
in parallel.
Also, in a sense there is no special support for "parallel" build in
Sage -- it's just that we have a way to override the make command via
an environment variable, and one can use that to make parallel make
happen. Using make instead of $MAKE in individual packages when
parallel make doesn't work is obviously hackish. The main problem
would be if you wanted to build on a system (e.g., freebsd) where gnu
make is called "gmake" and there is a system-wide "make" but it won't
work for building Sage. You would think doing export MAKE="gmake"
would be enough, but it wouldn't work.
-- William
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
