From owner-freebsd-ports@FreeBSD.ORG Wed Jan 28 07:43:15 2015 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2858351E for ; Wed, 28 Jan 2015 07:43:15 +0000 (UTC) Received: from smtp.infracaninophile.co.uk (smtp6.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3cd3:cd67:fafa:3d78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "ca.infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C1A5D99B for ; Wed, 28 Jan 2015 07:43:14 +0000 (UTC) Received: from worm.infracaninophle.co.uk (worm.infracaninophle.co.uk [81.2.117.101] (may be forged)) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.15.1/8.15.1) with ESMTPSA id t0S7h8BZ073299 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Wed, 28 Jan 2015 07:43:09 GMT (envelope-from m.seaman@infracaninophile.co.uk) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=infracaninophile.co.uk DKIM-Filter: OpenDKIM Filter v2.9.2 smtp.infracaninophile.co.uk t0S7h8BZ073299 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=infracaninophile.co.uk; s=201001-infracaninophile; t=1422430989; bh=T72WQe0BnvvTjx/y0HOpxItpKqqkIQv2OA/R19GjnkE=; h=Date:From:To:Subject:References:In-Reply-To; z=Date:=20Wed,=2028=20Jan=202015=2007:42:37=20+0000|From:=20Matthew =20Seaman=20|To:=20freebsd-ports@ freebsd.org|Subject:=20Re:=20Sprinkling=20WITH_OPENSSL_BASE=20in=2 0ports,=20ratbox=20build=20failure.|References:=20<54C87A38.307090 9@heuristicsystems.com.au>|In-Reply-To:=20<54C87A38.3070909@heuris ticsystems.com.au>; b=JtP5zozJ2uoR1aHoGbE0ckwGxGOnIZSLSSZA676Rx2dXhC06VOQWJTXU/V2u4z3Tm GXJy8ZptxJztoJn2Jd2enVVAfYay1khUQB+aCbRUxvdciIBIcC7PaXe6gAN0Z6X2NK afy4p/HSJTqQJkTZVkLpPNCOlNEpelOVn8rOI3YI= Message-ID: <54C892ED.80509@infracaninophile.co.uk> Date: Wed, 28 Jan 2015 07:42:37 +0000 From: Matthew Seaman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Subject: Re: Sprinkling WITH_OPENSSL_BASE in ports, ratbox build failure. References: <54C87A38.3070909@heuristicsystems.com.au> In-Reply-To: <54C87A38.3070909@heuristicsystems.com.au> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="JR5hNSBcCA6CUFWCCNPK7Xq9Tmok69vei" X-Virus-Scanned: clamav-milter 0.98.5 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU autolearn=ham autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on lucid-nonsense.infracaninophile.co.uk X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jan 2015 07:43:15 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --JR5hNSBcCA6CUFWCCNPK7Xq9Tmok69vei Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2015/01/28 05:57, Dewayne Geraghty wrote: > ratbox generated an unusual error message today, via portmaster on a > 10.1Stable, amd64 system > However commenting out the recently inserted > WITH_OPENSSL_BASE=3Dyes > from the Makefile enables the build to complete and uses the correct > crypto and ssl libraries. Shouldn't it be an option base or port? Or > is the openssl port going to go away? More like the other way around: ports will use the openssl version from ports exclusively, and the version in the base system will move into a private location. (This is my understanding of current thinking, but I make no guarantee that it is what does eventually get implemented.) The ircd-ratbox port doesn't appear to be doing anything unusual with respect to openssl support that I can see from a quick inspection of the port Makefile. If you've just added 'WITH_OPENSSL_BASE' to your make.conf, then (a) you potentially need to recompile many ports which depend on openssl so you don't end up with mixed linkage against both ports and base, and (b) some ports require the ports version of openssl because they depend on functionality only in the newer version available from ports. Personally, I prefer 'WITH_OPENSSL_PORT=3Dyes' It's meant I have been able to turn off SSLv2 and SSLv3 everywhere pretty simply (no more POODLE...) Cheers, Matthew --JR5hNSBcCA6CUFWCCNPK7Xq9Tmok69vei Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJUyJL2AAoJEABRPxDgqeTnIrcQAIB/RnZ4f2U7fCGvAM612HgW EM9rngo2dg11Cs30WEt5qB79znS3Rw6f4Sg9bfRhIwpMmsx2xuCyhyXTO9MJdyoI a3hulkiGR+H9dUhdeztJULpLp1iiDpU25OFwC0oYS+Bu2MyYRggSWyLNRUI8P356 /AmPaykoILzx1DC+HF6mrs40pFicvLYiqeR/+euJxLHTW3N8N/jBkBiyQPyFC0Ep YOcPcm2/rej/B7kjX9JTsPa/QKw+XwpCbAtWd1dfjDelSxrY5pZfQUOByCPpl7Vm vGVRp4SYZqRBX//gwP9TktTL1IZntpwuMYFYY1lb27e/5DgkYvTwMsvCHYVWNkFq +NrPpkCSvVs18xklym7cqbVqm6+zikj+9lJFjYZ1+ENQeWKb+mKtCKh7DB7A2/jY U5ELjXPxKlr8ADcYzxTaVTwKOaQy0omoaawPG9dffC1Q3ceRNKxFdI/esJkBu83T NKUTWuGfvDVcykw2Fgvf+3DPYRy+EwQltzekUcfVfA6jR/2u3SnmRy7T6m7asTXe SvO7K7DObsgD+Zh7L7QosEnqQlGJ1K4aBz9DAlCE993TZSQe6zUuTU3X51gi1ybG 1GFS1kkZd8DE3FrmDsAmkg/wLE9gUTlRJ+C9qFh1xZPRy1DTLoyaPifFk9TqDKCG HDlxEtPp4DU9a8EmY8NE =yWwv -----END PGP SIGNATURE----- --JR5hNSBcCA6CUFWCCNPK7Xq9Tmok69vei--