[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Problem with linking after system upgrade: "libssl not found"

From: Julian Foad <julianfoad_at_btopenworld.com>
Date: 2005-09-18 17:12:25 CEST

A few days ago I upgraded from SuSE Linux 9.1 to 9.3. After that I have been
unable to build Subversion properly. I have worked through some problems and
am left with a final link failure involving SSL:

> ------ completed all in neon
> cd subversion/clients/cmdline && /bin/sh /home/julianfoad/build/subversion/libtool --tag=CC --silent --mode=link gcc -Wall -Wundef -Wendif-labels -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wredundant-decls -Wnested-externs -g -Wmissing-declarations -pthread -DNEON_ZLIB -DSVN_DEBUG -DAP_DEBUG -Wpointer-arith -Wwrite-strings -Wshadow -rpath /usr/local/lib -o svn add-cmd.o blame-cmd.o cat-cmd.o checkout-cmd.o cleanup-cmd.o commit-cmd.o copy-cmd.o delete-cmd.o diff-cmd.o export-cmd.o help-cmd.o import-cmd.o info-cmd.o lock-cmd.o log-cmd.o ls-cmd.o main.o merge-cmd.o mkdir-cmd.o move-cmd.o notify.o prompt.o propdel-cmd.o propedit-cmd.o propget-cmd.o proplist-cmd.o props.o propset-cmd.o resolved-cmd.o revert-cmd.o status-cmd.o status.o switch-cmd.o unlock-cmd.o update-cmd.o util.o ../../../subversion/libsvn_client/libsvn_client-1.la ../../../subversion/libsvn_wc/libsvn_wc-1.la ../../../subversion/libsvn_ra/libsvn_ra-1.la ../../../subversion/libsvn_delta/libsvn_del
ta-1.la ../../../subversion/libsvn_subr/libsvn_subr-1.la /home/julianfoad/build/subversion/apr-util/libaprutil-1.la -ldb -lexpat /home/julianfoad/build/subversion/apr/libapr-1.la -lrt -lcrypt -lpthread -ldl /home/julianfoad/build/subversion/neon/src/libneon.la
> /usr/lib/gcc-lib/i586-suse-linux/3.3.5/../../../../i586-suse-linux/bin/ld: cannot find -lssl

The same happens whether I build with the in-tree neon or the installed neon
(which is 0.24.7). If I configure with in-tree neon and "--with-ssl" then
"configure" fails:

> checking for pkg-config... /usr/bin/pkg-config
> checking for openssl pkg-config data... no
> checking for library containing RSA_new... not found
> configure failed for neon

Yet package "openssl" is installed and the library is in a common place and
readable:

> ~> ls /usr/lib
> lrwxrwxrwx 1 root 15 2005-09-05 01:12 libssl.so.0 -> libssl.so.0.9.7
> -rwxr-xr-x 1 root 220185 2005-03-19 19:48 libssl.so.0.9.7

There doesn't seem to be a separate "openssl-devel" package.

Any ideas?

What was that library/linker configuration refreshing command that people are
often advised to run after the installed libraries have changed? Something
like "ldconfig" (which I don't have) or something to do with libtool?

- Julian

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Sep 18 17:13:11 2005

This is an archived mail posted to the Subversion Dev mailing list.