From: Joseph Myers <joseph@codesourcery.com>
To: Romain Naour <romain.naour@gmail.com>
Cc: <libc-alpha@sourceware.org>
Subject: Re: glibc 2.27: less than two weeks till release
Date: Tue, 30 Jan 2018 01:01:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1801292141480.28694@digraph.polyomino.org.uk> (raw)
In-Reply-To: <1356cb6f-70dc-53c6-881d-dda779c848fe@gmail.com>
On Mon, 29 Jan 2018, Romain Naour wrote:
> I'm not sure it worth the effort to keep the support for kernel headers between
> 4.4 and 4.9 (i.e: kernel not maintained anymore). Buildroot has already removed
> 4.5 to 4.8 kernel headers selection.
--enable-kernel is about the kernel supported at runtime, not about kernel
headers; it just so happened that in this case the mistake broke the
build with certain kernel headers. The oldest kernel version supported by
the glibc sources should always be an LTS version, but that doesn't stop
people using --enable-kernel with a more recent non-LTS version.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2018-01-29 21:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 17:56 Dmitry V. Levin
2018-01-18 21:56 ` TODO: Alternative month names (was: Re: glibc 2.27: less than two weeks till release) Rafal Luzynski
2018-01-18 22:04 ` Zack Weinberg
2018-01-18 23:07 ` Rafal Luzynski
2018-01-19 8:51 ` TODO: Alternative month names Carlos O'Donell
2018-01-19 10:41 ` Rafal Luzynski
2018-01-19 8:54 ` glibc 2.27: less than two weeks till release Carlos O'Donell
2018-01-21 22:01 ` Romain Naour
2018-01-22 11:11 ` Szabolcs Nagy
2018-01-22 11:53 ` Adhemerval Zanella
2018-01-22 12:08 ` Szabolcs Nagy
2018-01-22 15:49 ` Joseph Myers
2018-01-22 16:00 ` Florian Weimer
2018-01-22 15:45 ` Joseph Myers
2018-01-24 21:57 ` Romain Naour
2018-01-24 22:02 ` Joseph Myers
2018-01-28 17:35 ` Romain Naour
2018-01-29 20:30 ` Joseph Myers
2018-01-30 0:21 ` Romain Naour
2018-01-30 1:01 ` Joseph Myers [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=alpine.DEB.2.20.1801292141480.28694@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=romain.naour@gmail.com \
/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).