From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Priit Laes <plaes(at)plaes(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCH] Output configuration status after ./configure run. |
Date: | 2010-02-10 19:16:59 |
Message-ID: | 20100210191659.GP4922@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas escribió:
> On Wed, Feb 10, 2010 at 12:01 PM, Priit Laes <plaes(at)plaes(dot)org> wrote:
> >> Also, it's quite unclear which items deserve a place in the list.
> >> If it's just to repeat what was in the configure command-line, what
> >> is the value of that?
> >
> > It might avoid the 'FFFFUUUUUU, I forgot to enable python support.',
> > after you have waited a while for the build to finish...
>
> Hmm. That implies that you didn't look at the command that you typed
> but you did look at its output. I'm not going to say "no one does
> that" (who am I to judge?) but it seems kind of strange to me.
Maybe you didn't type it, but it came from elsewhere? Maybe you're
inheriting settings from some environment variable, or a file? Maybe
you're eval'ing pg_config --configure?
The general idea seems sensible to me. I can't comment on the
specifics.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-02-10 19:27:57 | Re: [PATCH] Output configuration status after ./configure run. |
Previous Message | Ivan Sergio Borgonovo | 2010-02-10 19:08:50 | I still didn't get how tsquery is internally |