public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Samuli Suominen <ssuominen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] heads up: glibc-2.20 will require >=linux-2.6.32
Date: Sun, 03 Aug 2014 16:19:54 +0300	[thread overview]
Message-ID: <53DE36FA.2010400@gentoo.org> (raw)
In-Reply-To: <1839476.CY3ocDWS18@vapier>


On 03/08/14 16:16, Mike Frysinger wrote:
> upstream glibc has dropped support for older Linux kernels.  your choices:
>  - upgrade your kernel
>  - switch to a different C library
>  - stick with glibc-2.19 for a while
>
> be warned though there are no plans atm to backport things to glibc-2.19.  
> this includes security fixes, but more importantly as time moves on, making 
> newer gcc versions sanely compile glibc.  we've kept older glibc versions 
> around to be nice, and on a part time basis for cross-compiling, but none of 
> those are given priority.  i.e. fixes come as people feel like doing them.
>
> certainly once glibc-2.20+ goes stable, there is no expectation let alone 
> requirement that packages in the tree be kept working with older glibc 
> versions.  the maintenance cost there is unreasonable.
>
> i guess if you're stuck on old crap, now would be a good time to start 
> preparing to unstick your crap.  glibc-2.20 will most likely be in ~arch in 
> the next 6 months.
> -mike

use of 2.6.32 needs ~sys-fs/udev-208 (kept around for late 2.6.32 patchsets)
use of current udev needs at least 2.6.39 for CONFIG_FHANDLE

so there's more problems with running such a old kernel than just glibc

just saying


  reply	other threads:[~2014-08-03 13:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-03 13:16 [gentoo-dev] heads up: glibc-2.20 will require >=linux-2.6.32 Mike Frysinger
2014-08-03 13:19 ` Samuli Suominen [this message]
2014-08-06  7:59 ` Tobias Klausmann

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=53DE36FA.2010400@gentoo.org \
    --to=ssuominen@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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