From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: libedit broke in head |
Date: | 2006-09-30 20:02:56 |
Message-ID: | 20060930200255.GC20466@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Stefan Kaltenbrunner wrote:
> Tom Lane wrote:
> > "Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> >> It seems I am unable to compile libedit support in -HEAD
> >
> > On what platform, and with what version of libedit? I built HEAD just
> > yesterday on a vanilla Darwin/Intel 10.4.7 machine with Apple's libedit.
>
> we have (a bit of) buildfarm coverage of that too - at least emu is
> building with --with-libedit-preferred for a while now.
>
> >
> >> Configured with:
> >> ./configure --with-libedit-preferred --without-readline
> >
> > Not sure that combination of switches is sensible. Try it with
> > just the first, or even without either if you don't have readline
> > present.
>
> I agree - using both flags together looks just wrong ...
I think the switches are confusing ... when you are using libedit, you
certainly don't want readline as well, so it seems natural to disable
it. I understand that what --without-readline really does is turn the
line-editing capability off in general rather than just readline, which
is confusing.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-09-30 20:36:56 | Re: libedit broke in head |
Previous Message | Tom Lane | 2006-09-30 19:21:17 | Re: Select for update with outer join broken? |