Re: Figured it out (psql and Gnu readline) - Mailing list pgsql-general

From Stephan Szabo
Subject Re: Figured it out (psql and Gnu readline)
Date
Msg-id 027c01bfec6c$21a07450$0c64010a@kick.com
Whole thread Raw
In response to Re: Figured it out (psql and Gnu readline)  (Erich <hh@cyberpass.net>)
List pgsql-general
Here's a stupid question,

What happens if you do the same kind of compile on a similar program from
your shell (a simple program that includes <readline/history.h>, with and
without -I/usr/local/include?
I'm just wondering if the compiler is not looking in /usr/local/include by
default and is not finding the header because of that...

----- Original Message -----
From: "Erich" <hh@cyberpass.net>
To: <tgl@sss.pgh.pa.us>
Cc: <pgsql-general@postgresql.org>
Sent: Wednesday, July 12, 2000 6:12 PM
Subject: Re: [GENERAL] Figured it out (psql and Gnu readline)


>
> > Well, that's darn peculiar.  configure.in has a test for
> > readline/history.h, big as life:
> > AC_CHECK_HEADERS(readline/history.h)
> > Does the config.log file show why it failed to find the include?
>
> Here's the lines from config.log:
>
> configure:2539: checking for main in -lreadline
> configure:2554: gcc -o conftest -O2 -pipe
   conftest.c -lreadline  -ltermcap -lcurses  1>&5
> configure:2582: checking for using_history in -lreadline
> configure:2601: gcc -o conftest -O2 -pipe
   conftest.c -lreadline  -lreadline -ltermcap -lcurses  1>&5
> configure:3833: checking for history.h
> configure:3843: gcc -E   conftest.c >/dev/null 2>conftest.out
> configure:3839: history.h: No such file or directory
> configure: failed program was:
> #line 3838 "configure"
> #include "confdefs.h"
> #include <history.h>
> configure:3873: checking for ieeefp.h
> configure:3883: gcc -E   conftest.c >/dev/null 2>conftest.out
> configure:3913: checking for limits.h
> configure:3923: gcc -E   conftest.c >/dev/null 2>conftest.out
> configure:3953: checking for netdb.h
> configure:3963: gcc -E   conftest.c >/dev/null 2>conftest.out
> configure:3993: checking for netinet/in.h
> configure:4003: gcc -E   conftest.c >/dev/null 2>conftest.out
> configure:4033: checking for readline.h
> configure:4043: gcc -E   conftest.c >/dev/null 2>conftest.out
> configure:4039: readline.h: No such file or directory
> configure: failed program was:
> #line 4038 "configure"
> #include "confdefs.h"
> #include <readline.h>
> configure:4073: checking for readline/history.h
> configure:4083: gcc -E   conftest.c >/dev/null 2>conftest.out
> configure:4079: readline/history.h: No such file or directory
> configure: failed program was:
> #line 4078 "configure"
> #include "confdefs.h"
> #include <readline/history.h>
> configure:4113: checking for readline/readline.h
> configure:4123: gcc -E   conftest.c >/dev/null 2>conftest.out
> configure:4153: checking for sys/select.h
> configure:4163: gcc -E   conftest.c >/dev/null 2>conftest.out
> configure:4193: checking for termios.h
> configure:4203: gcc -E   conftest.c >/dev/null 2>conftest.out
> configure:4233: checking for unistd.h
> configure:4243: gcc -E   conftest.c >/dev/null 2>conftest.out
> configure:4273: checking for values.h
> configure:4283: gcc -E   conftest.c >/dev/null 2>conftest.out
> configure:4279: values.h: No such file or directory
> configure: failed program was:
> #line 4278 "configure"
>
>
> > On my setup, which is readline 4.0 if I'm checking the right files,
> > HAVE_HISTORY_IN_READLINE does get defined, and AFAICT libhistory.a
> > doesn't get linked, but I most certainly do get history support.
> >
> > Which readline version are you using?  Maybe the GNU guys rearranged
> > which functions live in which library.  If so, we probably need
> > to be probing for a different symbol in libreadline to be compatible
> > across more libreadline versions ...
>
> I'm using readline 4.1, compiled from the distribution.  In other
> words, I didn't get it from /usr/ports, which is what OpenBSD normally
> uses.
>
> I have a stupid ./configure question: Whenever I compile something, I
> never want to have -g as a CC option.  How do I tell configure not to
> use -g as a CC option?  I only want -O2.  Usually I go through and
> edit Makefiles by hand after configure is done, but that's annoying.
>
> e
>



pgsql-general by date:

Previous
From: Froilan Mendoza
Date:
Subject: Re: PostgreSQL and Access (via ODBC)
Next
From: "Robert B. Easter"
Date:
Subject: Re: Triggers with arguments