Skip to content

Commit 2a3af43

Browse files
committed
Revert "autotools: don't link with -lcrypto twice."
This reverts commit 036fa9c. That doesn't work. We'd have to figure out what -I flag to use with that version of libcrypto and set the CFLAGS appropriately, and set HAVE_LIBCRYPTO to yes. If you have more than one non-system version of a library, hilarity is likely to ensure. Don't do that.
1 parent 036fa9c commit 2a3af43

File tree

1 file changed

+0
-20
lines changed

1 file changed

+0
-20
lines changed

configure.ac

Lines changed: 0 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -857,26 +857,6 @@ AC_ARG_WITH(crypto,
857857
want_libcrypto=ifavailable
858858
AC_MSG_RESULT([yes, if available])
859859
])
860-
if test "$want_libcrypto" != "no"; then
861-
#
862-
# Do we already *have* libcrypto, e.g. if we're using a
863-
# version of libpcap that has rpcap-over-TLS support?
864-
#
865-
AC_MSG_CHECKING([whether we're already linking with libcrypto])
866-
if $EGREP -s -q -e '-lcrypto|libcrypto' <<EOF
867-
$LIBS
868-
EOF
869-
then
870-
#
871-
# Yes; we already *have* libcrypto, don't
872-
# look for another one.
873-
#
874-
AC_MSG_RESULT([yes])
875-
want_libcrypto=no
876-
else
877-
AC_MSG_RESULT([no])
878-
fi
879-
fi
880860
if test "$want_libcrypto" != "no"; then
881861
#
882862
# Were we told where to look for libcrypto?

0 commit comments

Comments
 (0)