| 1 |
On 03/08/14 16:16, Mike Frysinger wrote: |
| 2 |
> upstream glibc has dropped support for older Linux kernels. your choices: |
| 3 |
> - upgrade your kernel |
| 4 |
> - switch to a different C library |
| 5 |
> - stick with glibc-2.19 for a while |
| 6 |
> |
| 7 |
> be warned though there are no plans atm to backport things to glibc-2.19. |
| 8 |
> this includes security fixes, but more importantly as time moves on, making |
| 9 |
> newer gcc versions sanely compile glibc. we've kept older glibc versions |
| 10 |
> around to be nice, and on a part time basis for cross-compiling, but none of |
| 11 |
> those are given priority. i.e. fixes come as people feel like doing them. |
| 12 |
> |
| 13 |
> certainly once glibc-2.20+ goes stable, there is no expectation let alone |
| 14 |
> requirement that packages in the tree be kept working with older glibc |
| 15 |
> versions. the maintenance cost there is unreasonable. |
| 16 |
> |
| 17 |
> i guess if you're stuck on old crap, now would be a good time to start |
| 18 |
> preparing to unstick your crap. glibc-2.20 will most likely be in ~arch in |
| 19 |
> the next 6 months. |
| 20 |
> -mike |
| 21 |
|
| 22 |
use of 2.6.32 needs ~sys-fs/udev-208 (kept around for late 2.6.32 patchsets) |
| 23 |
use of current udev needs at least 2.6.39 for CONFIG_FHANDLE |
| 24 |
|
| 25 |
so there's more problems with running such a old kernel than just glibc |
| 26 |
|
| 27 |
just saying |
Archives