From: Leo Famulari <leo@famulari.name>
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: 30537@debbugs.gnu.org
Subject: bug#30537: glibc 2.26 refuses to run on CentOS 6.8
Date: Tue, 20 Feb 2018 06:52:21 -0500 [thread overview]
Message-ID: <20180220115221.GA17373@jasmine.lan> (raw)
In-Reply-To: <20180220012229.GA28522@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 763 bytes --]
On Mon, Feb 19, 2018 at 08:22:29PM -0500, Leo Famulari wrote:
> 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.
As far as I can tell, the discussion started on the libc-alpha mailing
list in January 2016:
https://sourceware.org/ml/libc-alpha/2016-01/msg00885.html
... and continued into February:
https://sourceware.org/ml/libc-alpha/2016-02/msg00002.html
These messages can provide some useful context.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-02-20 11:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 18:46 glibc 2.26 refuses to run on CentOS 6.8 Ricardo Wurmus
[not found] ` <87d110stkn.fsf@mdc-berlin.de>
[not found] ` <87a7w4ssmx.fsf@mdc-berlin.de>
2018-02-19 19:41 ` bug#30537: " Ricardo Wurmus
[not found] ` <878tbosr7h.fsf@mdc-berlin.de>
2018-02-19 20:28 ` Jan Nieuwenhuizen
2018-02-21 23:12 ` Mark H Weaver
[not found] ` <87bmgiey3k.fsf@netris.org>
2018-02-22 20:30 ` Efraim Flashner
2018-02-23 22:01 ` bug#30537: Grafts vs. early bootstrapping packages Ludovic Courtès
2018-02-20 1:22 ` bug#30537: glibc 2.26 refuses to run on CentOS 6.8 Leo Famulari
2018-02-20 11:52 ` Leo Famulari [this message]
2018-02-20 12:34 ` Ricardo Wurmus
2018-02-20 12:51 ` Leo Famulari
2018-02-20 14:33 ` Ricardo Wurmus
2018-02-20 17:55 ` Ricardo Wurmus
2018-02-20 9:39 ` Efraim Flashner
2018-02-23 22:26 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180220115221.GA17373@jasmine.lan \
--to=leo@famulari.name \
--cc=30537@debbugs.gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).