[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Paralizing configure
From: |
Miles Bader |
Subject: |
Re: Paralizing configure |
Date: |
Wed, 9 Feb 2011 04:42:51 +0000 |
On Wed, Feb 9, 2011 at 4:39 AM, Ralf Corsepius <address@hidden> wrote:
>> At the least, constructs like
>> AC_CHECK_HEADERS([stdint.h unistd.h fcntl.h sys/mman.h sys/stat.h])
>> could check all the entries in parallel.
>
> Only simple scenarios, in which headers and header search paths are static -
> This often doesn't apply to complex configurations.
Wait, I'm confused ... how can the results of checking for "stdint.h"
affect the subsequent check for "unistd.h"?
[I meant, all the entries _within a single invocation_ (of
AC_CHECK_HEADERS, etc) could be checked in parallel...]
-miles
--
Cat is power. Cat is peace.
- Paralizing configure, Marian Marinov, 2011/02/08
- Re: Paralizing configure, Paul Eggert, 2011/02/08
- 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 <=
- 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
- Re: Paralizing configure, Ralf Wildenhues, 2011/02/14
Re: Paralizing configure, Bob Friesenhahn, 2011/02/09
Re: Paralizing configure, Javier Jardón, 2011/02/09