Thread: configure script problem

configure script problem

From
gfaruch@laposte.net (Grégory Faruch)
Date:
Bonjour,

The configure script have problems to find these functions : gettext,
using_history and cryp

My os is : solaris 9 on ultrasparc
postgres version : 7.2
my gcc version is : 3.1 (tested ok with s9)
readline version : 4.3
openssl version : 0.9.6c
gettext lib : i downloaded it from the postgres link

my variables :

LDFLAGS='-L/usr/local/lib -L/usr/local/ssl/lib -ltermcap -lreadline -
lhistory'
LD_LIBRARY_PATH=/usr/local/lib:/usr/local/ssl/lib
LD_RUN_PATH=/usr/local/lib
LD_OPTIONS='-L/usr/local/lib -L/opt/sfw/lib -R$ORIGIN/../lib -R/opt/sfw/lib
-R/opt/openssl/lib -R/usr/local/lib -i -s -z origin'

the configure call :

./configure --prefix=/usr/local/postgresql2 --with-
includes=/usr/local/include:/usr/local/ssl/include --with-
libs=/usr/local/lib:/usr/local/ssl/lib --enable-locale --enable-
multibyte=LATIN1 --enable-nls='fr' --with-java --enable-syslog

configure output :

        ##### ABOUT LIB PATHS #####

using LDFLAGS=-L/usr/local/lib -L/usr/local/ssl/lib -ltermcap -lreadline -
lhistory  -L/usr/local/lib -L/usr/local/ssl/lib

        ##### ABOUT READLINE LIB #####

checking for readline... yes (-lreadline)
checking for library containing using_history... none required (#????)

        ##### ABOUT SSL LIB #####

checking for library containing crypt... none required

        ##### ABOUT GETTEXT LIB #####

checking for library containing gettext... none required

checking for libintl.h... yes

I tried with different version of gcc readline and gettext but configure
says always the same.
You can find a copy of an xterm session which show result of 'set' command and
the entire configure output here : www.gdf.xdir.org

I wonder if 'crle' command can play any role to solve my problem ?

Thanks for reading.

Grégory

Re: configure script problem

From
Tom Lane
Date:
gfaruch@laposte.net (=?ISO-8859-1?Q?Gr=E9gory_Faruch?=) writes:
> checking for readline... yes (-lreadline)
> checking for library containing using_history... none required (#????)

Why do you think this is a problem?  It looks fine to me.

            regards, tom lane