On Sat, 17 Mar 2012 14:09:17 +0000 Paul Howarth <p...@city-fan.org> wrote:
> I've been trying to build libssh2 (1.4.0) against openssl 1.0.1 in > Fedora Rawhide and it fails to build because global.c calls > _libssh2_init_aes_ctr but that function isn't defined in openssl.c if > HAVE_EVP_AES_128_CTR is defined, resulting in: > > /bin/sh ../libtool --tag=CC --mode=link gcc -O2 -g -pipe -Wall > -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector > --param=ssp-buffer-size=4 -m64 -mtune=generic -Wl,-z,relro -o > direct_tcpip direct_tcpip.o ../src/libssh2.la libtool: link: gcc -O2 > -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector > --param=ssp-buffer-size=4 -m64 -mtune=generic -Wl,-z -Wl,relro > -o .libs/direct_tcpip direct_tcpip.o ../src/.libs/libssh2.so > -Wl,-rpath -Wl,/usr/lib64 ../src/.libs/libssh2.so: undefined > reference to `_libssh2_init_aes_ctr' collect2: error: ld returned 1 > exit status > > So I tried patching global.c not to call _libssh2_init_aes_ctr if > HAVE_EVP_AES_128_CTR is defined, which fixed the compile problem but > broke the test suite: > (snip) I'm able to work around this for now by disabling the AES-CTR detection in configure, by doing: export ac_cv_func_EVP_aes_128_ctr=no before running the configure script, so it doesn't try to use the openssl functions. Paul. _______________________________________________ libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
