Installation on CentOS 5.2 (readline trouble) - Mailing list pgsql-general

From Carlos Moreno
Subject Installation on CentOS 5.2 (readline trouble)
Date
Msg-id 48EAB8B8.4030107@mochima.com
Whole thread Raw
Responses Re: Installation on CentOS 5.2 (readline trouble)  ("Scott Marlowe" <scott.marlowe@gmail.com>)
Re: Installation on CentOS 5.2 (readline trouble)  (Greg Smith <gsmith@gregsmith.com>)
Re: Installation on CentOS 5.2 (readline trouble)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Hi,

I just downloaded the latest, 8.3.4, and I'm trying to install it on
a CentOS 5.2 machine with all the updates  (64-bit --- the system
is an Opteron DC)

The configure script fails reporting it doesn't find readline.

The package readline-devel *is* installed, and indeed the .so
file is under /usr/lib and /usr/lib64

The problem seems to be with readline dependencies:  if I try
a dummy program (i.e., a file with a main that says return 0;)
and compile it with readline:

[ ... ]$ gcc -o tt test.c -lreadline

I get the following bunch of errors:

 gcc -o tt test.c -lreadline
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../lib64/libreadline.so:
undefined reference to `PC'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../lib64/libreadline.so:
undefined reference to `tgetflag'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../lib64/libreadline.so:
undefined reference to `tgetent'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../lib64/libreadline.so:
undefined reference to `UP'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../lib64/libreadline.so:
undefined reference to `tputs'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../lib64/libreadline.so:
undefined reference to `tgoto'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../lib64/libreadline.so:
undefined reference to `tgetnum'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../lib64/libreadline.so:
undefined reference to `BC'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../lib64/libreadline.so:
undefined reference to `tgetstr'

I know the problem seems to be more a CentOS or RH specific
thing, than a PostgreSQL specific one, but I guess someone out
here may have run into this, and perhaps have some suggestions?

I also tried with libedit  (downloaded it from sourceforge, since I
could not find RPM packages native to the distribution).  Anyway,
I get the exact same error --- configure reports the same error, and
the little test program, when compiled with -ledit instead of
-lreadline, produces almost the same error messages (six of the
above lines --- the ones in lowercase, coincidentally)

The installation was completed with the switch --without-readline,
except that the functionality is somwhat crippled, so I'd much
rather avoid the issue.

Thanks for any tips/pointers!

Carlos
--


pgsql-general by date:

Previous
From: Ben Chobot
Date:
Subject: Re: Can update triggers detect the column in the update statement?
Next
From: Martin Gainty
Date:
Subject: Re: Can update triggers detect the column in the update statement?