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

From: Priit Laes <plaes(at)plaes(dot)org>
To:
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] Output configuration status after ./configure run.
Date: 2010-02-10 17:01:19
Message-ID: 1265821279.3650.16.camel@chi
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Ühel kenal päeval, K, 2010-02-10 kell 10:39, kirjutas Tom Lane:
> 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.

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 ;)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-02-10 17:05:54 Re: Some belated patch review for "Buffers" explain analyze patch
Previous Message Alvaro Herrera 2010-02-10 16:58:34 Re: Some belated patch review for "Buffers" explain analyze patch