From: Sebastian L. <seb...@mm...> - 2004-08-15 16:26:41
|
* Huub Reuver wrote: > The problem is that linux/include is usually a snapshot from the > kernelsources used when compiling the C-library. The reason the > header-file misses is simply because it only recently became changed, > after some clean-ups in the kernel. [...] > I'm not very much into development, but wasn't the rule that modules > can depend on in-kernel headerfiles while userland programs depend > on linux/include? I can only tell about how Debian does this: We have a kernel-headers package for each kernel version and arch specific revision and a linux-kernel-headers package which installs kernel headers corresponding to the installed glibc package. The module must of course be built against a configured kernel-tree with the exact version for which the module will later be deployed. Instead of supplying complete configured kernel-trees for each kernel version and arch revision distros provide only the headers to build external kernel modules against. However these headers usually contain only the contents of linux/include whereas the abovementioned ieee802_11.h resides in linux/drivers/net/wireless. So this is not a problem of unmatching kernel versions but of this file just not being packaged and thus is unavailable in most distributions. For the Debian packages I maintain I just copied the header file from a recent kernel source into my source package. I hope this is going to work as the protocol API should not change dramtically ;-) Regards, Sebastian -- PGP-Key: http://www.mmweg.rwth-aachen.de/~sebastian.ley/public.key Fingerprint: A46A 753F AEDC 2C01 BE6E F6DB 97E0 3309 9FD6 E3E6 |