| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Greg Smith <greg(at)2ndquadrant(dot)com>, �������� <shiweidong2009(at)foxmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: getaddrinfo.c error |
| Date: | 2009-12-16 22:53:41 |
| Message-ID: | 1261004022.15029.3.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On mån, 2009-12-14 at 09:27 -0500, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2009-12-16 22:56:55 | Re: Dependency tracking tool |
| Previous Message | Mike Christensen | 2009-12-16 22:49:54 | Re: Need some advice on a difficult query |