RE: Compilation de PostGreSQL
> -----Message d'origine-----
> De : Patrice OLIVER [mailto:patrice.oliver@ch-beaune.fr]
> Envoyé : jeudi 10 juin 2004 15:51
> À : debian-user-french@lists.debian.org
> Objet : Compilation de PostGreSQL
>
>
> Bonjour,
>
> Sur ma debian woody, je souhaite compiler la v7.4.2 de PostGreSQL.
>
> lorsque je fait un ./configure --enable-thread-safety, j'obtiens celà :
>
> checking build system type... i686-pc-linux-gnu
> checking host system type... i686-pc-linux-gnu
> checking which template to use... linux
> checking whether to build with 64-bit integer date/time support... no
> checking whether NLS is wanted... no
> checking for default port number... 5432
> checking for gcc... gcc
> checking for C compiler default output... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking how to turn off strict aliasing in gcc... -fno-strict-aliasing
> configure: using CFLAGS=-O2 -fno-strict-aliasing
> checking whether the C compiler still works... yes
> checking how to run the C preprocessor... gcc -E
> checking allow thread-safe client libraries... yes
> checking whether to build with Tcl... no
> checking whether to build with Tk... no
> checking whether to build Perl modules... no
> checking whether to build Python modules... no
> checking whether to build Java/JDBC tools... no
> checking whether to build with Kerberos 4 support... no
> checking whether to build with Kerberos 5 support... no
> checking whether to build with PAM support... no
> checking whether to build with Rendezvous support... no
> configure: using CPPFLAGS=-D_GNU_SOURCE
> configure: using LDFLAGS=
> checking for gawk... no
> checking for mawk... mawk
> checking for flex... /usr/bin/flex
> checking whether ln -s works... yes
> checking for ld used by GCC... /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... yes
> checking for ranlib... ranlib
> checking for lorder... lorder
> checking for tar... /bin/tar
> checking for strip... strip
> checking whether it is possible to strip libraries... yes
> checking for bison... bison -y
> checking for perl... /usr/bin/perl
> checking for main in -lbsd... no
> checking for setproctitle in -lutil... no
> checking for main in -lm... yes
> checking for main in -ldl... yes
> checking for main in -lnsl... yes
> checking for main in -lsocket... no
> checking for main in -lipc... no
> checking for main in -lIPC... no
> checking for main in -llc... no
> checking for main in -ldld... no
> checking for main in -lld... no
> checking for main in -lcompat... no
> checking for main in -lBSD... no
> checking for main in -lgen... no
> checking for main in -lPW... no
> checking for main in -lresolv... yes
> checking for library containing getopt_long... none required
> checking for main in -lunix... no
> checking for library containing crypt... -lcrypt
> checking for library containing fdatasync... none required
> checking for shmget in -lcygipc... no
> checking for readline... no
> configure: error: readline library not found
> If you have readline already installed, see config.log for details on the
> failure. It is possible the compiler isn't looking in the proper
> directory.
> Use --without-readline to disable readline support.
>
>
> Ce qui me gêne, c'est :
> checking for library containing getopt_long... none required
> checking for library containing fdatasync... none required
>
> Je ne trouve pas les librairies associées. Quelqu'un peut m'aider ?
Pourquoi est-ce que ça te gêne ?
Ca veut simplement dire que ton système supporte cette option
et qu'il n'a justement pas besoin de librairie.
Par contre tu devrais installer quelquechose comme "readline dev"
Mickaël
Reply to: