-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Someone recently reported an inability to specify the prefix for libssl.

It seems the culprit is somehow the multiple invocation of the macro
AC_LIB_HAVE_LINKFLAGS, even though they appear in exclusive conditional
sections.

If one removes the invocation of this macro from the gnutls-testing
section, leaving the only invocation as the one in the openssl-testing
section, openssl is detected normally. However, even if one replaces the
invocation of AC_LIB_HAVE_LINKFLAGS() in the gnutls section with one
identical to the way it is used in the openssl section, the one in the
openssl section will fail.

I'm not sure how this is happening, but part of the failure is that, in
the generated "configure" shell script, $shextlib gets an empty value
instead of "so", and the openssl test winds up looking for
"/usr/local/lib/libssl." instead of "/usr/local/libssl.so", and of
course fails to find it, so it doesn't get added to the library flags to
the test-run of gcc for the libssl test program.

I'm hoping that someone with a little more knowledge of our m4 macros
and autoconf might be able to figure out what's going on with that.

- --
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer...
http://micah.cowan.name/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGtM0u7M8hyUobTrERCFdXAJ4v9SSexm0yu14YkTYtW9VLRnV+lwCfZjjE
Bh3NhWfr/ANLD6ZyKbIvlP0=
=I1Bs
-----END PGP SIGNATURE-----

Reply via email to