> There's some shortcuts you maybe can take when compiling natively, with
> appropriate kernel sources around, but these are shortcuts not portable
> solutions.
>
> The proper solution is probably a helper program, supplied with
> glibc, which reads the appropriate kernel includes and generates
> the corresponding glibc includes. Also, there should be a "linux
> kernel version" supplied with these glibc includes which you can test
> numerically with #if.
As the time passes, the kernel evolves and new ioctls appear. But it's still
a good idea to compile programs for older kernels (e.g., for stable ones)
without having to override which ioctls/sockopts/whatever are supported
by the target system. So it would be better to separate the kernel includes
from glibc includes and release them as a separate package and just choose
the right one when compiling stuff.
Have a nice fortnight
-- Martin `MJ' Mares <mj@ucw.cz> http://atrey.karlin.mff.cuni.cz/~mj/ Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth "How much wood would a woodchuck chuck if a woodchuck could chuck wood?"- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu