[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Paralizing configure

From: Marian Marinov
Subject: Re: Paralizing configure
Date: Wed, 9 Feb 2011 02:38:16 +0200
User-agent: KMail/1.13.5 (Linux/; KDE/4.5.5; i686; ; )

On Tuesday 08 February 2011 22:51:20 Paul Eggert wrote:
> On 02/08/11 12:46, Ralf Wildenhues wrote:
> > external tools like that or 'make' are pretty much dead in the water
> > with current Autoconf implementation because we do not have any idea of
> > what shell variables are needed in the environment for the next tests.
> Oh yes, I quite agree, it would require a real change to
> the Autoconf implementation, and people who write tests
> would have to be disciplined about their dependencies.
> The default would be sequential, for backward compatibility,
> but if someone goes to the work to declaring their dependencies,
> we could assume that it could be slotted into a make -j
> or whatever.
> None of this stuff would be a breeze, of course.
> > (Not to speak of 32K environment+command line length on MSYS.)
> We'd have to stay sequential in limited environments like that.
> That's OK.

We can start a new branch and see if it is worth the work. And if it is ok we 
can then start the upgrade of all the code.

I'm sure that there would be situations in which the tests must remain 
sequental. However we can isolate them into bigger independent sections of 

Best regards,
Marian Marinov

Attachment: signature.asc
Description: This is a digitally signed message part.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]