Akim Demaille writes:
> Both: by accident what you propose is having ./config.status kill
> itself by running configure which creates it. So by design, it is
> avoided.
But 'config.status --recheck' *does* recreate config.status.
--
Peter Eisentraut [EMAIL PROTECTED]
Bob Friesenhahn <[EMAIL PROTECTED]> wrote in
[EMAIL PROTECTED]:">news:[EMAIL PROTECTED]:
> On a related topic, the message printed by 'config.status --recheck'
> is incorrect. The message printed is not properly quoted. For
> example:
>
> % ./config.status --recheck
> running /bin/bash /home/
On 13 Oct 2002, Akim Demaille wrote:
> > "Bob" == Bob Friesenhahn <[EMAIL PROTECTED]> writes:
>
> Bob> I have learned the hard way that 'config.status --recheck'
> Bob> produces incomplete results as compared to the original
> Bob> 'configure' that created config.status. I assume that this i
> "Bob" == Bob Friesenhahn <[EMAIL PROTECTED]> writes:
Bob> I have learned the hard way that 'config.status --recheck'
Bob> produces incomplete results as compared to the original
Bob> 'configure' that created config.status. I assume that this is
Bob> because config.status runs configure wit
I have learned the hard way that 'config.status --recheck' produces
incomplete results as compared to the original 'configure' that
created config.status. I assume that this is because config.status
runs configure with the extra options '--no-create --no-recursion'.
Is this shortcoming by design
