Quote:
Originally Posted by NiLuJe
@knc1: Well, of course I'm assuming you're running a kernel >= your kernel headers  . |
Have been thinking a bit more about what I wrote . . . .
That was probably a poor example to have used as an example.
But the principle remains, if your c library has no connection to a feature, your code can't use it because of the missing code path in the library.
And for the case of the KT-v5.1.0 the kernel is newer (I.E: supporting of) the older header defined functions.
I don't expect any problems on this front.
Unless we build something against 3.0 headers and expect it to work on 2.6.31
