Re: [PATCH] Output configuration status after ./configure run.

Поиск
Список
Период
Сортировка
Искать
От
Priit Laes
Тема
Re: [PATCH] Output configuration status after ./configure run.
Дата
Msg-id
1265821279.3650.16.camel@chi
Ответ на
Список
Дерево обсуждения
[PATCH] Output configuration status after ./configure run. Priit Laes <plaes@plaes.org>
Re: [PATCH] Output configuration status after ./configure run. Tom Lane <tgl@sss.pgh.pa.us>
Re: [PATCH] Output configuration status after ./configure run. Priit Laes <plaes@plaes.org>
Re: [PATCH] Output configuration status after ./configure run. "Ross J. Reedstrom" <reedstrm@rice.edu>
Re: [PATCH] Output configuration status after ./configure run. Robert Haas <robertmhaas@gmail.com>
Re: [PATCH] Output configuration status after ./configure run. Alvaro Herrera <alvherre@commandprompt.com>
Re: [PATCH] Output configuration status after ./configure run. Euler Taveira de Oliveira <euler@timbira.com>
Re: [PATCH] Output configuration status after ./configure run. Peter Eisentraut <peter_e@gmx.net>
Re: [PATCH] Output configuration status after ./configure run. Alvaro Herrera <alvherre@commandprompt.com>
Re: [PATCH] Output configuration status after ./configure run. Robert Haas <robertmhaas@gmail.com>
Re: [PATCH] Output configuration status after ./configure run. Tom Lane <tgl@sss.pgh.pa.us>
Re: [PATCH] Output configuration status after ./configure run. Priit Laes <plaes@plaes.org>
Re: [PATCH] Output configuration status after ./configure run. Robert Haas <robertmhaas@gmail.com>
Re: [PATCH] Output configuration status after ./configure run. Euler Taveira de Oliveira <euler@timbira.com>
Re: [PATCH] Output configuration status after ./configure run. Alvaro Herrera <alvherre@commandprompt.com>
Re: [PATCH] Output configuration status after ./configure run. Robert Haas <robertmhaas@gmail.com>
Re: [PATCH] Output configuration status after ./configure run. Robert Haas <robertmhaas@gmail.com>
Ühel kenal päeval, K, 2010-02-10 kell 10:39, kirjutas Tom Lane:
> Priit Laes  writes:
> > This patch enables showing configure status at the end of ./configure
> > run and thus makes ./configure process a bit easier to follow (in the
> > sense of what features are actually enabled).
> 
> I don't think anybody actually reads configure's output anyway, so I'm
> not sure about the point of this.  Usually you wish you knew this
> information long afterwards.  We do have tools (pg_config,
> pg_controldata) for extracting such information from an existing
> installation, which is the real use-case IMHO.

I do. And there are probably others. It provides a list of nicely
formatted options that configure enabled/disabled before you start the
build process. pg_config and pg_controldata are a bit too late.

> 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...

Cheers,
Priit ;)

В списке pgsql-hackers по дате отправления
От: Alvaro Herrera
Дата:
От: Ross J. Reedstrom
Дата:
FAQ