From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: 01/02: gnu: libressl: Update to 2.5.3. Date: Thu, 13 Apr 2017 16:18:24 -0400 Message-ID: <20170413201824.GA23404@jasmine> References: <20170412011114.29557.46901@vcs0.savannah.gnu.org> <20170412011115.CE2FF220BE@vcs0.savannah.gnu.org> <87pogioukr.fsf@netris.org> <20170412152029.GA5920@jasmine> <87mvbkny4y.fsf@gnu.org> <20170413185921.GD14931@jasmine> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="J2SCkAp4GZ/dPZZf" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58296) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cylCM-0000F0-16 for guix-devel@gnu.org; Thu, 13 Apr 2017 16:18:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cylCI-00009z-Ts for guix-devel@gnu.org; Thu, 13 Apr 2017 16:18:34 -0400 Content-Disposition: inline In-Reply-To: <20170413185921.GD14931@jasmine> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ludovic =?iso-8859-1?Q?Court=E8s?= Cc: guix-devel@gnu.org --J2SCkAp4GZ/dPZZf Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 13, 2017 at 02:59:21PM -0400, Leo Famulari wrote: > On Thu, Apr 13, 2017 at 05:08:29PM +0200, Ludovic Court=E8s wrote: > > A simple approach is to force LibreSSL to always use its non-getentropy > > code, and lift this restriction once we clearly require newer kernels= =B9. > > The attached patch does that. > >=20 > > Thoughts? >=20 > > + ;; Do as if 'getentropy' was missing since older Linux kernels la= ck it > > + ;; and libc would return ENOSYS, which is not properly handled. > > + '(#:configure-flags '("ac_cv_func_getentropy=3Dno"))) >=20 > If we are committed to building glibc with the 2.6 kernel headers, and > to providing substitutes for libressl and it's dependent packages, then > I think this patch is a good option. >=20 > But, it's a bit of a shame to leave this ~2.5 year old feature behind, > especially when the 2.6 Linux series is not even part of the Linux > long-term-support project. [0] These kernels *will* live for a long time > through support from RHEL; their most recent kernel on RHEL7 is 3.10. >=20 > However, I don't fully understand the impact of building glibc with a > newer set of headers, so my objection is a weak one :) After reading more, I realized that my knowledge on this topic was even weaker than I thought. So please disregard what I wrote here. --J2SCkAp4GZ/dPZZf Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAljv3QoACgkQJkb6MLrK fwhxgQ/8Dqp+zY2gx5siQ3XfNLPC57brfcHAdIXX/Ey7e+VHfSPmfGJftihJJO/e piEkEBdZeo9gPBrIqi3YgpbAVc5HBRsNK31h3LDaNmnfSCDOK8xRtJb0kAyexKz+ Of4FtdsdcZlLTgctV39q9gwLath7RVPa2MKSFF1HLHpwfINrYuANH2dGmhtBFaR1 Tzc7iPetBEtSgHTTyZs/8YRHp1WYK9TeMdHspH9DaNkLHbnS08CfSifaopaJ+5Gy JF7ITjkWorxKS86HWOqwCiCfdricz0S+beOY7+YX52GkGuvsSJA0xuSV9jgyGzmu BPijPKE0DRE0TyPzJqeK/P23jkonVFSs8xf8YzOVCnQCmIWprjXWlOI6n1Z3jkdg udhFLGKYEtZ4SxThYdkFAH0cWzJwbGT6lmqW6Is6j3pv8x7S33xuAO4M+TvLBoji 0jdwcHFgf28QSTo5bU4dK+FRc33belTVDR8vZMCd035m5ZSpJSWlps1uMMlapwhT bxN7je9Gc5UQmr204oMsWIvU62SoFEJ5K/bmCDd30d8ThKCPHXfDJwTpH0WcQ4aC YZHIUdSb7yvyKkVGDMrFYpJGXQKpHUDKWJ6BOHaaHe7X9XpipdGezKwOYXNFeBOs ThoBnzExfeQ9q3UBNb6h1aF+5EKj3/EJlYY1LfxCmS8wXgU/NwE= =JP3j -----END PGP SIGNATURE----- --J2SCkAp4GZ/dPZZf--