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