[Top][All Lists]

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

Re: Running a plain ./config.status at top level

From: Alexandre Duret-Lutz
Subject: Re: Running a plain ./config.status at top level
Date: Wed, 09 Apr 2003 20:34:24 +0200
User-agent: Gnus/5.090016 (Oort Gnus v0.16) Emacs/21.2 (gnu/linux)

Hi Akim,

>>> "Akim" == Akim Demaille <address@hidden> writes:


 Akim> The idea is that we should probably run plain ./config.status at the
 Akim> top level update of Makefile.

Tom attempted to fix PR/46 (subdir5.test) with a similar patch last year.

The above thread lists a few drawbacks.  I think the most
important one (besides not really fixing PR/46) is that always
running a plain ./config.status when $(top_srcdir)/
changes can take _minutes_ in a very large project, when only
_one_ file really has to be rebuilt (the top-level Makefile).

I think running a plain `./config.status' makes sense only when
`config.status' has changed.  Perhaps we should start playing
with `$?'.  If `config.status' appears in `$?', then run it
without argument, otherwise run it only for the current
directory.  Does it seem sensible?  I guess this scheme could be
done in _all_ directories, not only the top-level.  Maybe this
would also fix PR/46 (I haven't thought about that much).
Alexandre Duret-Lutz

reply via email to

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