Re: 'configure' bug on Mac OS X 10.3.5

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Neil Conway <neilc(at)samurai(dot)com>
Cc: "Fahad G(dot)" <Fahad(dot)Gilani(at)anusf(dot)anu(dot)edu(dot)au>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: 'configure' bug on Mac OS X 10.3.5
Date: 2004-10-15 04:47:49
Views: Raw Message | Whole Thread | Download mbox
Lists: pgsql-bugs

Neil Conway <neilc(at)samurai(dot)com> writes:
> On Wed, 2004-10-13 at 10:23, Fahad G. wrote:
>> I checked and I don't have 'readline' installed. --without-readline did the
>> trick, but shouldn't this be handled automatically?

> This is intentional

Indeed. A few releases back we did actually behave that way (drop the
readline functionality and continue) but it was persuasively argued that
this was a Bad Thing. To see why, you should consider the fact that
configure is often run in non-interactive contexts (such as RPM package
construction) where its output isn't likely to be scrutinized by humans.
RPM package makers would much rather get a build failure than have the
thing bull ahead and build a substandard RPM. Even when configure *is*
invoked interactively, the output isn't likely to be scrutinized
closely; and a newbie may not understand the implications of a bleat in
the output even if he reads it.

So basically, the opinion around here is that if you want a build with
nonfunctional readline capability, you need to say so on the configure
command line. The default assumption is that you want readline, and
we aim to do that or die trying.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Neil Conway 2004-10-15 05:21:02 Re: SELECT FOR UPDATE and LIMIT 1 behave oddly
Previous Message Tom Lane 2004-10-15 04:22:33 Re: SELECT FOR UPDATE and LIMIT 1 behave oddly