Re: Detecting readline in configure

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Detecting readline in configure
Date: 2001-05-21 17:48:59
Message-ID: Pine.LNX.4.30.0105211945000.757-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane writes:

> I suggest that the behavior of configure not be changed, but that it be
> tweaked to put out a slightly more obvious notice about not being able
> to find readline support. Maybe
>
> checking for libreadline ... no
> checking for libedit ... no
> *
> * NOTICE: I couldn't find libreadline nor libedit. You will
> * not have history support in psql.
> *

This may be useful as well, but it doesn't help those doing unattended
builds, such as RPMs and *BSD ports. In that case you need to abort to
notify the user that things didn't go the way the package maker had
planned.

Let's do both.

--
Peter Eisentraut peter_e(at)gmx(dot)net http://funkturm.homeip.net/~peter

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mikheev, Vadim 2001-05-21 17:52:28 RE: Plans for solving the VACUUM problem
Previous Message Bruce Momjian 2001-05-21 17:42:40 Re: AW: Fix for tablename in targetlist