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 обсуждение исходный текст |
Ответ на | Re: [PATCH] Output configuration status after ./configure run. (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [PATCH] Output configuration status after ./configure run.
Re: [PATCH] Output configuration status after ./configure run. |
Список | pgsql-hackers |
Ühel kenal päeval, K, 2010-02-10 kell 10:39, kirjutas Tom Lane: > Priit Laes <plaes@plaes.org> 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 по дате отправления: