[Date Prev][Date Next] [Chronological] [Thread] [Top]

Build fails to build shared libraries (ITS#2331)



Full_Name: Ken Hall
Version: 2.0.27
OS: Linux-390 (SuSE 7.2)
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (199.43.32.21)


Configure of Openldap 2.0.11 displays the following:

checking dynamic linker characteristics... GNU ld.so
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for objdir... .libs
checking for dlopen in -ldl... yes
checking for dlfcn.h... yes
checking whether a program can dlopen itself... yes
checking whether a statically linked program can dlopen itself... no
creating libtool
not updating unwritable cache ./config.cache

Build of 2.0.27 with same configure parms gives:

checking if the linker (/usr/s390-suse-linux/bin/ld) is GNU ld... yes
checking whether the linker (/usr/s390-suse-linux/bin/ld) supports shared
libraries... yes
checking command to parse /usr/bin/nm -B output... ok
checking how to hardcode library paths into programs... immediate
checking for /usr/s390-suse-linux/bin/ld option to reload object files... -r
checking dynamic linker characteristics... no
checking if libtool supports shared libraries... no
checking whether to build shared libraries... no
checking whether to build static libraries... yes
checking for objdir... .libs
checking for dlopen in -ldl... yes
checking for dlfcn.h... yes
checking whether a program can dlopen itself... yes
checking whether a statically linked program can dlopen itself... no
creating libtool
not updating unwritable cache ./config.cache

Both done on the same system.  libtool is 1.3.5.  Shared libraries are not
built, but files are created with names containing '?' and '*'.