On Fri, Mar 14, 2003 at 12:09:48PM +0100, Götz Babin-Ebell wrote:
> Christian Knoke wrote:
> >On Fri, Mar 14, 2003 at 12:04:42AM +0100, Götz Babin-Ebell wrote:
>
> >>In you old mail you had:
>
> >>>make[2]: Entering directory `/home/chris/tmp/curl-7.10.3/src'
> >>>/bin/sh ../libtool --mode=link gcc -g -O2 -L/usr/ssl/lib -o curl
> >> ^^^^^^^^^^^^
>
> >>>main.o
> >>>hugehelp.o urlglob.o writeout.o writeenv.o ../lib/libcurl.la -lz -lssl
> >>>-lcrypto -ldl -lz
> >>>gcc -g -O2 -o .libs/curl main.o hugehelp.o urlglob.o writeout.o
> >>>writeenv.o
> >>>-L/usr/ssl/lib ../lib/.libs/libcurl.so -lz -lz -lz -lssl -lcrypto -ldl
> >>>-lz
> >>>.../lib/.libs/libcurl.so: undefined reference to `UI_OpenSSL'
>
> >>The includes are in /usr/include but the library is in /usr/ssl/lib ?
>
> >Hhm, /usr/ssl/lib/ exists but is empty here.
>
> So the OpenSSL library is got from the directory /usr/lib...

Yes.

> >>Please, what is your compile option ?
> >>gcc ... -I/usr/include -I/usr/ssl/include ... ?
>
> >Not sure what you mean. In the Makefile is a line:
> >
> >CPPFLAGS = -I/usr/ssl/include/openssl -I/usr/ssl/include
>
> So you get your OpenSSL headers from /usr/ssl/include and your
> library from /usr/lib ?

No, they are in /usr/include/openssl

Main part is resolved now:

While the static libcrypto.a was up to date, there were old versions of
libcrypto.so and libssl.so of 0.9.6 hanging around in /usr/lib.

I removed them, and was able to compile curl with this configuration:

CPPFLAGS="-I/usr/include/openssl -I/usr/include" LDFLAGS="-L/usr/lib" \
./configure --prefix=/usr --with-ssl=/usr/ssl

make completed ok, but warnings like this had been given:

gcc -g -O2 -o .libs/lib504 lib504.o first.o -L/usr/lib -L/usr/ssl/lib
../../lib/.libs/libcurl.so -lz -lz -lz -lssl -lcrypto -ldl -lz
/usr/i486-suse-linux/bin/ld: warning: libssl.so.0.9.6, needed by
../../lib/.libs/libcurl.so, not found (try using -rpath or -rpath-link)
/usr/i486-suse-linux/bin/ld: warning: libcrypto.so.0.9.6, needed by
../../lib/.libs/libcurl.so, not found (try using -rpath or -rpath-link)
creating lib504

I didn't test whether curl was operating, though.

Reinstall of openssl 0.9.7a, this time *with* shared libraries, made the
warnings disappear, and curl is operating.

Unfortunately, mutt stopped working after the remove of libcrypto.so.0.9.6

That is why my /usr/lib is looking like this now:

max:/usr/lib # ls -l libcrypto* libssl*
-rw-r--r-- 1 root root 1772324 Mar 14 12:45 libcrypto.a
lrwxrwxrwx 1 root root 14 Mar 14 12:45 libcrypto.so -> libcrypto.so.0
lrwxrwxrwx 1 root root 18 Mar 14 12:45 libcrypto.so.0 -> libcrypto.so.0.9.7
-rwxr-xr-x 1 root root 922986 Sep 24 2001 libcrypto.so.0.9.6
-r-xr-xr-x 1 root root 1160211 Mar 14 12:45 libcrypto.so.0.9.7
-rw-r--r-- 1 root root 272216 Mar 14 12:45 libssl.a
lrwxrwxrwx 1 root root 11 Mar 14 12:45 libssl.so -> libssl.so.0
lrwxrwxrwx 1 root root 15 Mar 14 12:45 libssl.so.0 -> libssl.so.0.9.7
-rwxr-xr-x 1 root root 205656 Sep 24 2001 libssl.so.0.9.6
-r-xr-xr-x 1 root root 214805 Mar 14 12:45 libssl.so.0.9.7

I guess I have to recompile mutt to let it use 0.9.7.

Thanks for your help.

Christian

-- 
Christian Knoke     * * *      http://www.enter.de/~c.knoke/
* * * * * * * * *  Ceterum censeo Microsoft esse dividendum.
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en