_Applications_ should not use kernel headers at all. For ioctls, they
should ship with copies of the definitions they need. That's been made
clear as crystal many times on this list, and it should be in the FAQ if
it isn't already.
> Saying "oh, but applications should do that" isn't much of a argument,
> as there isn't a better way of working out where a set of kernel
> headers are. And "oh but applications should be using /usr/include/"
> doesn't cut it. There are times when you really do need to be able to
> build things outside of the kernel tree that are kernel specific.
Sorry, I don't understand your message.
Are you saying, for third-party kernel modules, "oh well, use `uname
-r`", "don't use `uname -r`", "use something else" or "I don't have any
suggestions"?
-- Jamie
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/