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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Priit Laes <plaes(at)plaes(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] Output configuration status after ./configure run.
Date: 2010-02-10 15:39:14
Message-ID: 16536.1265816354@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Priit Laes <plaes(at)plaes(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-02-10 15:58:52 Re: buildfarm breakage
Previous Message Magnus Hagander 2010-02-10 15:27:59 Re: buildfarm breakage