The most recent glibc ebuild (sys-libs/glibc-2.3.6-r3) sets NPTL_KERNEL_VERSION to 2.6.9, so it refuses to proceed if the ntpl USE flag is set and the kernel is below 2.6.9. The previous ebuild (sys-libs/glibc-2.3.6-r2) sets NPTL_KERNEL_VERSION to 2.6.6. I searched all the bugs, changelogs, CVS logs, etc., and could not find anywhere an explanation of why 2.6.6 became 2.6.9. I'm running coLinux which provides its own kernel, which happens to be a heavily patched version of Linux 2.6.8.1. At the current time, it is extremely problematic for me to upgrade beyond this kernel version. I've been using NPTL successfully with this kernel for a long time now and have never had any trouble with it. So I am confused as to why someone thinks that kernel version 2.6.9 is needed. Why was NPTL_KERNEL_VERSION raised for this latest glibc ebuild? Can someone please add an explanation to the ebuild, preferably with a pointer to a bug number or a discussion thread somewhere containing further details?
(In reply to comment #0) > > Why was NPTL_KERNEL_VERSION raised for this latest glibc ebuild? Can > someone please add an explanation to the ebuild, preferably with a > pointer to a bug number or a discussion thread somewhere containing > further details? > http://forums.gentoo.org/viewtopic-t-376943.html * --enable-kernel bumped to 2.6.9 or 2.611. This prevents glibc from compiling in compatibility cruft making it leaner and meaner. Of course you need to be running a 2.6.9 or 2.6.11 kernel at least.
Extra Futex parameters was added during 2.6.7 and I think 2.6.8 .. just set NPTL_KERNEL_VERSION in your make.conf if an issue.
