From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: bug#30537: glibc 2.26 refuses to run on CentOS 6.8 Date: Tue, 20 Feb 2018 18:55:48 +0100 Message-ID: <87sh9vr1ej.fsf@mdc-berlin.de> References: <87eflgstqt.fsf@mdc-berlin.de> <20180220012229.GA28522@jasmine.lan> <20180220115221.GA17373@jasmine.lan> <87woz7rga4.fsf@mdc-berlin.de> <20180220125136.GA7573@jasmine.lan> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51846) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eoCA7-0005pJ-Po for bug-guix@gnu.org; Tue, 20 Feb 2018 12:57:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eoCA2-00065H-RB for bug-guix@gnu.org; Tue, 20 Feb 2018 12:57:07 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:45247) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eoCA2-000657-Gi for bug-guix@gnu.org; Tue, 20 Feb 2018 12:57:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1eoCA2-0006wu-9A for bug-guix@gnu.org; Tue, 20 Feb 2018 12:57:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: 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" Cc: 30537@debbugs.gnu.org Ricardo Wurmus writes: > Leo Famulari writes: > >>> For future updates to the glibc we would have to re-evaluate if the >>> current RHEL 6.x kernel still supports all features the glibc expects, >>> and decide once more if we can justify patching glibc to allow that one >>> particular kernel version. >> >> Yes... and this will probably continue for many years. But I do think we >> should do something to work around the issue now, and reevaluate our >> solution when the pressure is off. >> >> It would be nice if the graft only applied to x86_64-linux, but I've >> never considered if that is easy to do or not. > > I don’t know if we can graft a package only for a single architecture. > At least at the time of ungrafting we could apply the patch only on > x86_64 (and only rebuild the world for that architecture). > > FWIW: I’ve applied this patch to the installation at the MDC and it > works fine. The biggest downside here is the slowness of grafts over > NFS (I still need to update the protocol to NFS 4.1) and the many lines > of output that are amplified by communicating with a remote daemon. > > Other than that I’m happy that this crisis could be temporarily averted. > > I’d like to have this in master, though, so that people can run “guix > pull” again and actually get working software. I should note that now every Guix command first prints this: GC Warning: pthread_getattr_np or pthread_attr_getstack failed for main thread I suspect that this is not good. Guix was built with the grafted glibc. -- Ricardo