On mån, 2009-12-14 at 09:27 -0500, Tom Lane wrote:
> Alvaro Herrera <alvherre@commandprompt.com> writes:
> > Tom Lane wrote:
> >> Hm, I wonder whether the reason the OP ran into trouble was that he
> >> followed that guide :-(. Relying on manual invocation of configure
> >> is a sure recipe for hitting weird breakage anytime somebody changes
> >> the configure input files ... Surely there's a way to teach Eclipse
> >> to do that when needed?
>
> > Is this really a problem? I think our makefiles are set up such that
> > they will re-run configure in some of its input files have changed.
>
> I believe they will re-run config.status to regenerate the output
> files. This is not the same thing as re-running the configure script.
It runs config.status --recheck and then config.status for the output
files, which is ultimately pretty much the same as rerunning configure.
