From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: bug#30537: glibc 2.26 refuses to run on CentOS 6.8 Date: Mon, 19 Feb 2018 20:22:29 -0500 Message-ID: <20180220012229.GA28522@jasmine.lan> References: <87eflgstqt.fsf@mdc-berlin.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="jRHKVT23PllUwdXP" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55813) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1enwe8-00046K-V9 for bug-guix@gnu.org; Mon, 19 Feb 2018 20:23:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1enwe6-0000iC-Ag for bug-guix@gnu.org; Mon, 19 Feb 2018 20:23:04 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:44004) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1enwe6-0000i4-2v for bug-guix@gnu.org; Mon, 19 Feb 2018 20:23:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1enwe5-00044m-TQ for bug-guix@gnu.org; Mon, 19 Feb 2018 20:23:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <87eflgstqt.fsf@mdc-berlin.de> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ricardo Wurmus Cc: 30537@debbugs.gnu.org --jRHKVT23PllUwdXP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 19, 2018 at 07:46:02PM +0100, Ricardo Wurmus wrote: > The NixOS developers patch glibc to make sure that all software still > runs on Linux 2.6.32: >=20 > https://raw.githubusercontent.com/NixOS/nixpkgs/master/pkgs/developme= nt/libraries/glibc/allow-kernel-2.6.32.patch >=20 > Can we please also apply this? Without this Guix on HPC is pretty much > dead at the MDC. My questions are, how does the glibc team choose the minimum kernel version? What could go wrong if we apply this patch and somebody uses Guix on a pre-3.2.0 kernel? Perhaps they simply chose to not support glibc on any kernel that is not supported upstream; 3.2.x is the oldest supported release series. But, we should have some idea of their reasoning, in my opinion. --jRHKVT23PllUwdXP Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAlqLeFIACgkQJkb6MLrK fwgZsRAA4XKbDixlu85agTzhMnjIUFwE1XKvFcPGrIo2YPVLi4A9d5dmgpaZ1UDn urruOghvw6k1k+SBGQrmCKbkVcXrdVGCvPaBdhDHTdLGLWx3R+K8KaSgzVsUz3YT lJDcxE4utIil3C0ow/tHHgFhfGpqkdotA8XDKCS9B5mPZaXv0XLekTqb6RQ9hOOX cAnuOV5ZdaOBo0YvlGcYSMzY66fmaCNVHgtGzJM6w7UW4hrJdkvh1fzyF9Piw0k3 j756f5JCbZYd2g2zy/4L7jsKuqW8STmAeMx95b5s34Fwa0flBHdh0NjVo63WKT9c KoUq9Xh/Ab9Nj+I3IyKef+7TpoBxOGMYNd+BB3CnB1U0gfnh2VsSbpu+KS4Eh2wB L7xl70XNCLBNm8ixAmfPicsD0ttrqNM9X2oWZ0F8KyWZXMFlJRFyZblKoj5HFc/0 XdoJecVfuj+lt95BVVldED9zd9JiGdLdgw8NY8ZKxNHbUI8PtXoXaTjObQq9wjK/ M9tYrv2JZdFusH8LAvVO7WhcxyWHoBNLbp05GUIiPs++jsfV1G1e69zhDoPBu0t5 3CM+1v9bDA7SHLPFN43RgBV60pR0ol+/C/ObL6KxlODl+fzsXt4DIeGY9BYaGr96 OkGzcKiA7HvOMlTGUNC9/xdMTa+o0DwpOdour22btLl52CCJjxI= =wNoz -----END PGP SIGNATURE----- --jRHKVT23PllUwdXP--