[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Paralizing configure
From: |
Paul Eggert |
Subject: |
Re: Paralizing configure |
Date: |
Tue, 08 Feb 2011 12:39:21 -0800 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7 |
On 02/08/11 02:55, Marian Marinov wrote:
> My idea is to split the tests that configure dose into different sections.
> And
> paralize the tests in each seaction. Then if one test returns false the whole
> section should be considered for retesting.
Although that might help a bit, I expect it's too much work, because people
will have to go through by hand and parallelize their code. I expect it'd be
better if 'configure' were parallelized by default, much as makefiles are,
with the programmers mentioning explicit dependencies as necessary.
- Paralizing configure, Marian Marinov, 2011/02/08
- Re: Paralizing configure,
Paul Eggert <=
- Re: Paralizing configure, Ralf Wildenhues, 2011/02/08
- Re: Paralizing configure, Paul Eggert, 2011/02/08
- Re: Paralizing configure, Marian Marinov, 2011/02/08
- Re: Paralizing configure, Miles Bader, 2011/02/08
- Re: Paralizing configure, Ralf Corsepius, 2011/02/08
- Re: Paralizing configure, Miles Bader, 2011/02/08
- Re: Paralizing configure, Peter Rosin, 2011/02/09
- Re: Paralizing configure, Miles Bader, 2011/02/09
- Re: Paralizing configure, Peter Rosin, 2011/02/09
- Re: Paralizing configure, Ralf Wildenhues, 2011/02/10