Cameron Gregg wrote:
Tony Earnshaw wrote:
ons, 15.09.2004 kl. 03.55 skrev Kurt D. Zeilenga: [...]
configure is looking for the library version to match the header version (and, subsequently, for that version to be appropriate).
Indeed ... I never did GNU compiles on Solaris, but FWIW I get exactly the same error as Greg when compiling Openldap source on RedHat RHAS/RHEL3 unless I put /path/to/BerkeleyDB.4.2/lib into /etc/ld.so.conf and run ldconfig, even though I give the LDFLAGS path to configure. Perhaps if I included -ldb-4.2 to link against work; as it is, I use ld.so.conf.
Does Solaris have any similar library definition config arrangement?
--Tonni
yes. crle
# crle
Configuration file [3]: /var/ld/ld.config Default Library Path (ELF): /usr/lib:/usr/local/lib Trusted Directories (ELF): /usr/lib/secure (system default)
Command line: crle -c /var/ld/ld.config -l /usr/lib:/usr/local/lib
#
Cam
YES!!!!! adding it to the system library path worked. Thank you!
$ crle
Configuration file [3]: /var/ld/ld.config Default Library Path (ELF): /usr/lib:/usr/local/lib:/usr/local/BerkeleyDB.4.2/lib Trusted Directories (ELF): /usr/lib/secure (system default)
Command line: crle -c /var/ld/ld.config -l /usr/lib:/usr/local/lib:/usr/local/BerkeleyDB.4.2/lib
$
make is executing as I write this :-)
Slighty off topic, can anyone remember the program on solaris you can run that shows the libraries that an executable is linked to?
it's used like so:
#unknownProgramName executableFilename
Thanks to everyone for their help.
Cam