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

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Priit Laes <plaes(at)plaes(dot)org>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] Output configuration status after ./configure run.
Date: 2010-02-11 16:17:38
Message-ID: 603c8f071002110817x178a0e4fiee31558ca7d39102@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Feb 11, 2010 at 2:30 AM, Priit Laes <plaes(at)plaes(dot)org> wrote:
> Also:
>> Hmm.  That implies that you didn't look at the command that you typed
>> but you did look at its output.  I'm not going to say "no one does
>> that" (who am I to judge?) but it seems kind of strange to me.
>
> Yes, strange but I don't really make the connection of blindly typing
> the command and figuring out what options configure supports... :S

Well if you want to know what options it supports just do ./configure --help ...

...Robert

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-02-11 16:17:40 Re: Avoiding bad prepared-statement plans.
Previous Message Robert Haas 2010-02-11 16:16:36 Re: TCP keepalive support for libpq