From: Stefan Liebler <stli@linux.ibm.com>
To: Xi Ruoyao <xry111@xry111.site>,
GNU C Library <libc-alpha@sourceware.org>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>
Subject: Re: Question: Is there a plan when to require a higher Linux kernel version than 3.2?
Date: Tue, 20 Sep 2022 11:56:56 +0200 [thread overview]
Message-ID: <8840df45-4a87-ec98-62c2-886ef8a7e138@linux.ibm.com> (raw)
In-Reply-To: <e17c33f2ea54e185d1ed0277afab02d1c0c9e574.camel@xry111.site>
On 20/09/2022 11:40, Xi Ruoyao wrote:
> On Tue, 2022-09-20 at 11:11 +0200, Stefan Liebler via Libc-alpha wrote:
>> Hi,
>>
>> the minimum required Linux kernel version is currently 3.2 which was set
>> with commit 5b4ecd3f95695ef593e4474b4ab5a117291ba5fc
>> "Require Linux 3.2 except on x86 / x86_64, 3.2 headers everywhere." back
>> in 2016.
>>
>> Is there a plan when to require a higher Linux kernel version and which
>> version will then be used as minimum?
>>
>> Some background on my question:
>> On s390x, unfortunately the direct socket syscalls are not used due to
>> the __ASSUME_* macro undefines in
>> sysdeps/unix/sysv/linux/s390/kernel-features.h if Linux kernel version
>> <4.3 is used.
>
> You can use --enable-kernel=4.3 in your build if you won't use it on
> Linux < 4.3.
>
Yes, you are right.
For my custom build I can use this configure flag.
But I think the distros will configure glibc either with their own
defined kernel-version or will align to the minimum kernel version used
with glibc-upstream.
next prev parent reply other threads:[~2022-09-20 9:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 9:11 Stefan Liebler
2022-09-20 9:40 ` Xi Ruoyao
2022-09-20 9:56 ` Stefan Liebler [this message]
2022-09-21 16:50 ` Joseph Myers
2022-09-21 23:07 ` Michael Hudson-Doyle
2022-09-22 16:59 ` Joseph Myers
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=8840df45-4a87-ec98-62c2-886ef8a7e138@linux.ibm.com \
--to=stli@linux.ibm.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=xry111@xry111.site \
/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.
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).