From: Ben Hutchings <ben-/+tVBieCtBitmTQ+vhA3Yw@public.gmane.org>
To: Greg Thelen <gthelen-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
klibc mailing list
<klibc-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [klibc] [ANNOUNCE] klibc 2.0.13
Date: Mon, 31 Jul 2023 14:58:26 +0200 [thread overview]
Message-ID: <2179500f1c35299452d1e1dc04e85145bb6f5fed.camel@decadent.org.uk> (raw)
In-Reply-To: <xr93edko8x8v.fsf-70RgUwATE2L0OAmNFB7Q3HdI/KCU8OHYLMHrShElKjA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 482 bytes --]
On Sun, 2023-07-30 at 22:29 -0700, Greg Thelen wrote:
[...]
> Is there a minimum kernel that klibc is expected to build against? I ask
> because klibc-2.0.13 includes a change that requires kernel 5.11+.
[...]
I don't currently keep track of what the minimum version is. But in
general, you should expect it to require a recent version at both
compile- and run-time.
Ben.
--
Ben Hutchings
Design a system any fool can use, and only a fool will want to use it.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-07-31 12:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 1:00 [ANNOUNCE] klibc 2.0.13 Ben Hutchings
[not found] ` <688a7863c7023794bb8e93b6d526e8fab4336fb2.camel-/+tVBieCtBitmTQ+vhA3Yw@public.gmane.org>
2023-07-31 5:29 ` [klibc] " Greg Thelen
[not found] ` <xr93edko8x8v.fsf-70RgUwATE2L0OAmNFB7Q3HdI/KCU8OHYLMHrShElKjA@public.gmane.org>
2023-07-31 12:58 ` Ben Hutchings [this message]
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=2179500f1c35299452d1e1dc04e85145bb6f5fed.camel@decadent.org.uk \
--to=ben-/+tvbiectbitmtq+vha3yw@public.gmane.org \
--cc=gthelen-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=klibc-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org \
/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).