Re: [PATCH] Output configuration status after ./configure run.
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Priit Laes <plaes@plaes.org>
Cc: pgsql-hackers@postgresql.org
Date: 2010-02-10T15:39:14Z
Lists: pgsql-hackers
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. 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? regards, tom lane