From: Ricardo Wurmus <rekado@elephly.net>
To: Danny Milosavljevic <dannym@scratchpost.org>
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 22:22:28 +0100 [thread overview]
Message-ID: <87606ssmi3.fsf@elephly.net> (raw)
In-Reply-To: <20180219202838.5c5358ce@scratchpost.org>
Hi Danny,
> Can you try just passing --enable-kernel=2.6.32 to "configure" of glibc instead?
>
> It should set the minimal version without any weird patching.
Does this work even though the official minimum kernel version for glibc
2.26 is 3.2.0?
> But newer glibc has moved a lot of kernel definitions into glibc, might cause a
> problem if glibc just assumes it's all there but in fact it's not there at
> runtime (like the recent Haskell problem etc).
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.
There are additional notes on how that was done:
# HOWTO: check glibc sources for changes in kernel requirements
git log -p glibc-2.25.. sysdeps/unix/sysv/linux/x86_64/kernel-features.h sysdeps/unix/sysv/linux/kernel-features.h
# get kernel sources (update the URL)
mkdir tmp && cd tmp
curl http://vault.centos.org/6.9/os/Source/SPackages/kernel-2.6.32-696.el6.src.rpm | rpm2cpio - | cpio -idmv
tar xf linux-*.bz2
# check syscall presence, for example
less linux-*?/arch/x86/kernel/syscall_table_32.S
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.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2018-02-19 21:38 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 [this message]
2018-02-19 22:46 ` Danny Milosavljevic
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 ` 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=87606ssmi3.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=30537@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
--cc=guix-devel@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 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.