Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
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

pgsql-hackers by date

Next:From: Tom LaneDate: 2010-02-10 15:58:52
Subject: Re: buildfarm breakage
Previous:From: Magnus HaganderDate: 2010-02-10 15:27:59
Subject: Re: buildfarm breakage

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group