From: Danny Milosavljevic <dannym@scratchpost.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org, Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>,
30537@debbugs.gnu.org
Subject: Re: glibc 2.26 refuses to run on CentOS 6.8
Date: Mon, 19 Feb 2018 23:46:03 +0100 [thread overview]
Message-ID: <20180219234603.69a821a7@scratchpost.org> (raw)
In-Reply-To: <87606ssmi3.fsf@elephly.net>
Hi Ricardo,
> Does this work even though the official minimum kernel version for glibc
> 2.26 is 3.2.0?
I think so, BUT the patchset looks pretty similar to what would happen
if you specified the configure flag except for one spot.
So maybe Nix found out some ill effects.
The most worrying part in glibc is
#if __LINUX_KERNEL_VERSION < 0x040300
# undef __ASSUME_ACCEPT4_SYSCALL
# undef __ASSUME_SENDMSG_SYSCALL
# undef __ASSUME_RECVMSG_SYSCALL
# undef __ASSUME_CONNECT_SYSCALL
# undef __ASSUME_RECVFROM_SYSCALL
# undef __ASSUME_SENDTO_SYSCALL
#endif
So that would have to be watched out for.
__ASSUME_CONNECT_SYSCALL is some scary stuff. Getting it wrong could break all
networking in the system.
> The Red Hat kernels are a bit special in that they are not just old
> kernels, but heavily patched to work with newer software. The Nix
> people wrote that they have confirmed that 2.6.32 works up to
> glibc-2.26-131.
Oh, I didn't know that. If it's tested that way, let's use it that way
for the time being.
> If there was a way to test for kernel features instead of looking at the
> kernel version I’d do that instead of looking for a way to relax the
> lower kernel version bound.
Yeah...
next prev parent reply other threads:[~2018-02-19 22:46 UTC|newest]
Thread overview: 23+ 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
2018-02-19 18:49 ` Ricardo Wurmus
2018-02-19 19:09 ` Ricardo Wurmus
2018-02-19 19:28 ` Danny Milosavljevic
2018-02-19 21:22 ` Ricardo Wurmus
2018-02-19 22:46 ` Danny Milosavljevic [this message]
2018-02-19 19:41 ` bug#30537: " Ricardo Wurmus
2018-02-19 19:41 ` Ricardo Wurmus
2018-02-19 20:28 ` bug#30537: " Jan Nieuwenhuizen
2018-02-21 23:12 ` Mark H Weaver
2018-02-22 20:30 ` Efraim Flashner
2018-02-22 20:30 ` Efraim Flashner
2018-02-23 22:01 ` bug#30537: Grafts vs. early bootstrapping packages Ludovic Courtès
2018-02-21 23:12 ` bug#30537: glibc 2.26 refuses to run on CentOS 6.8 Mark H Weaver
2018-02-20 1:22 ` Leo Famulari
2018-02-20 11:52 ` Leo Famulari
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
2018-02-23 22:26 ` bug#30537: " 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180219234603.69a821a7@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=30537@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.