| |||||||||||||
|
| |||||||||||||
The 2.6.20 cycle beginsThe 2.6.20 cycle beginsPosted Dec 7, 2006 12:06 UTC (Thu) by dlang (✭ supporter ✭, #313)In reply to: The 2.6.20 cycle begins by nix Parent article: The 2.6.20 cycle begins
the kernel headers are not intended to be used by any userspace program, including glibc. so what 'broke' is something that's not supposed to work in the first place.
even gentoo doesn't compile anything against the kernel headers directly, they maintain a seperate package that's the headers that userspace needs extracted out of the kernel headers.
unless the kernel changes an interface that's exported to userspace (which would be a break of backwards compatability), or glibc is trying to take advantage of a new interface that's exported to userspace there is no reason to change glibc when a new kernel is installed (including no need to recompile it)
if glibc is trying to take advantage of a new interface then it's up to glibc to be able to use the right headers.
David Lang
(Log in to post comments)
The 2.6.20 cycle begins Posted Dec 8, 2006 0:43 UTC (Fri) by nix (subscriber, #2304) [Link] Sheesh, pay attention to developments in the kernel tree. `makeheaders_check' and `make headers_install' exists since 2.6.19 and is *explicitly intended* for generating a /usr/include/{linux,asm*,...} tree to be used to build glibc and other programs that have to communicate using the APIs which are, like it or not, defined in those headers (ioctl()s anyone?).
The previous system was not scalable: even major distributors were using
As David Woodhouse (I think it was) put it recently, `the days of `throw
The 2.6.20 cycle begins Posted Dec 8, 2006 13:11 UTC (Fri) by dlang (✭ supporter ✭, #313) [Link] from what I have seen of this, the headers made by make headers_check are not yet expected to bedirectly useable (after all, this is the first release of a major new feature)
the intention is that eventually this will make a set of headers that don't need any manual masaging before they can be used, but everyone recognises that they aren't there yet, it's just a starting pooint for the distros to use when makeing their kernel headers packages
it's also hard to call the introduction of a feature like this that has never existed before a major breakage in the kernel, the new feature may not work yet, but I don't see how it can be called a regression when it never existed before.
|
|
||||||||||||