On Fri, Aug 09, 2002 at 02:29:13PM -0400, Josh Huber wrote: > You definately should not do it that way. The kernel headers in > /usr/include are the headers libc was built against, and these should > be updated with libc. I like how the README and the Makefile for > wireless-tools claim that distribitions which do this are broken, and > suggest copying the wireless.h file into /usr/include. WTF? > > You should just build the wireless-tools against the correct kernel > includes, by specifying (usually in the makefile) the location of the > kernel source you want to build with. Since the wireless-tools has no > mechanism to do this, just add: > > -I/path/to/kernel/source/include/ > > to the proper place in the makefile. (i.e. to the CFLAGS variable)
Can I take it this is also the appropriate way to compile the mol-modules-sources? They're (I believe) expecting /usr/include/linux and /usr/include/asm to be symlinks to the /usr/src/kernel-sources... hierarchy. Zac
