security/libssh2: fix the GCRYPT option

The port uses the old crypto configure flags:
--with-libgcrypt and --with-openssl. These flags
are no longer supported.

Besides from the obvious effect of the actual port configuration
not matching user intent, it also produces incorrect pkg-config
file for the given set of dependencies, and other ports that
depend on libssh2 fail when it's configured with GCRYPT=on.

Fix by using the proper configure arguments:
--with-crypto=libgcrypt and --with-crypto=openssl.

PR:		248164
Submitted by:	dgilbert@eicat.ca (bug report), James French (patch)
Approved by:	maintainer timeout
This commit is contained in:
Roman Bogorodskiy 2020-08-08 05:17:01 +00:00
parent 3721a69cd2
commit 66e4a27d1d
Notes: svn2git 2021-03-31 03:12:20 +00:00
svn path=/head/; revision=544360

View File

@ -3,7 +3,7 @@
PORTNAME= libssh2
PORTVERSION= 1.9.0
PORTREVISION= 2
PORTREVISION= 3
PORTEPOCH= 3
CATEGORIES= security devel
MASTER_SITES= https://www.libssh2.org/download/ \
@ -27,8 +27,8 @@ TRACE_DESC= Enable debug packet traces
TRACE_CONFIGURE_ENABLE= debug
GCRYPT_LIB_DEPENDS= libgcrypt.so:security/libgcrypt
GCRYPT_CONFIGURE_ON= --with-libgcrypt
GCRYPT_CONFIGURE_OFF= --with-openssl
GCRYPT_CONFIGURE_ON= --with-crypto=libgcrypt
GCRYPT_CONFIGURE_OFF= --with-crypto=openssl
GCRYPT_CPPFLAGS= -I${LOCALBASE}/include
GCRYPT_LIBS= -L${LOCALBASE}/lib
GCRYPT_USES_OFF= ssl