From owner-freebsd-ports@freebsd.org Sat Jul 2 02:25:49 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9B266B8F835 for ; Sat, 2 Jul 2016 02:25:49 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (unknown [IPv6:2602:304:b010:ef20::f2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gw.catspoiler.org", Issuer "gw.catspoiler.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6F25F2E2C for ; Sat, 2 Jul 2016 02:25:49 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.15.2/8.15.2) with ESMTP id u622Pfbc094491; Fri, 1 Jul 2016 19:25:45 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <201607020225.u622Pfbc094491@gw.catspoiler.org> Date: Fri, 1 Jul 2016 19:25:41 -0700 (PDT) From: Don Lewis Subject: Re: what to do when base openssl isn't suitable To: jbeich@vfemail.net cc: freebsd-ports@FreeBSD.org In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Jul 2016 02:25:49 -0000 On 2 Jul, Jan Beich wrote: > Don Lewis writes: > >> I've got a port that does not work with base openssl because it looks >> for libssl.pc. Other than that, I don't think it is picky about what >> flavor of ports ssl is installed. Because the default version of ssl >> still defaults to base, I don't see a way to get this port to build on >> the cluster, so there is no way to provide binary packages. That's a >> problem for end users because this port has bunch of huge build >> dependencies. Thoughts? > > Have you tried putting a copy of libssl.pc under ${FILESDIR} and > adjusting PKG_CONFIG_PATH or forcing configure to accept *FLAGS without? > > # from net-p2p/zetacoin/Makefile > CONFIGURE_ENV= CRYPTO_CFLAGS="-I${OPENSSLINC}" CRYPTO_LIBS="-L${OPENSSLLIB} -lcrypto" \ > SSL_CFLAGS="-I${OPENSSLINC}" SSL_LIBS="-L${OPENSSLLIB} -lssl" > > # from mail/mpop/Makefile > OPENSSL_CONFIGURE_ENV=${OPENSSLINC:M/usr/include:C,.+,libssl_CFLAGS=" ",} \ > ${OPENSSLLIB:M/usr/lib:C,.+,libssl_LIBS="-lssl -lcrypto",} Option #2 works, except on FreeBSD 9, where the base version of OpenSSL is too old. I'm ok with setting IGNORE in that case.