Re: [PATCH] Output configuration status after ./configure run. - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [PATCH] Output configuration status after ./configure run.
Date
Msg-id 20100210191659.GP4922@alvh.no-ip.org
Whole thread Raw
In response to Re: [PATCH] Output configuration status after ./configure run.  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [PATCH] Output configuration status after ./configure run.
Re: [PATCH] Output configuration status after ./configure run.
List pgsql-hackers
Robert Haas escribió:
> On Wed, Feb 10, 2010 at 12:01 PM, Priit Laes <plaes@plaes.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.


pgsql-hackers by date:

Previous
From: Ivan Sergio Borgonovo
Date:
Subject: I still didn't get how tsquery is internally
Next
From: Robert Haas
Date:
Subject: Re: [PATCH] Output configuration status after ./configure run.