Re: readline selection (was Re: [GENERAL] psql leaking? - SOLVED) - Mailing list pgsql-bugs

From Peter Eisentraut
Subject Re: readline selection (was Re: [GENERAL] psql leaking? - SOLVED)
Date
Msg-id 200409050850.00860.peter_e@gmx.net
Whole thread Raw
In response to readline selection (was Re: [GENERAL] psql leaking? - SOLVED)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: readline selection (was Re: [GENERAL] psql leaking? - SOLVED)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Tom Lane wrote:
> (1) modify PGAC_CHECK_READLINE so that it really does prefer readline
> over libedit consistently.  I think all this would take is switching
> the loop order:
>
> for pgac_rllib in -lreadline -ledit ; do
>   for pgac_lib in "" " -ltermcap" " -lncurses" " -lcurses" ; do
>
> but possibly I'm missing something.

That seems reasonable.  I'm not really sure why the loops are nested the
other way.

> (2) fix the readline header selection so that it will only take the
> headers that correspond to the selected library.  These libraries are
> more or less source-compatible but they do not have the same ABI, so
> mix-and-match is not going to work.

That sounds like a pretty hard problem to solve.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

pgsql-bugs by date:

Previous
From: Michael Fuhr
Date:
Subject: Re: Permissions problem with sequences
Next
From: Harald Armin Massa
Date:
Subject: Failed to connect to database - further investigations