Hi,
>>"Kevin" == Kevin M Bealer <[EMAIL PROTECTED]> writes:
Kevin> But will it break anything major if I don't follow this
Kevin> guideline, and esp. is there a temporary way to set things up
Kevin> 'the old way'? Most of what I compile right now wants kernel
Kevin> headers so it can be compatible with the current kernel (ie
Kevin> kernel utilities and patches.) For example I have kernel
Kevin> utilities which use #include<linux/something.h> and I keep
Kevin> catching them raiding the /usr/include directory.
If you *sure* you need the latest kernel headers, (and that means
that you should put a test in preinst that tests that the correct
version is running with uname -r (if that is not necessary, you
should rethink whether you really need the very latest), then the
accepted method is to just use -I/usr/src/linux/include in the
appropiate CFLAGS (provided that kernel-headers or kernel-source
exists on the system)
Most programs, even if they include <linux/something.h>, do
not really depend on the version of the kernel, as long as the kernel
versions are not too far off, they will work. And the headers
provided in libc5-dev are just that.
manoj
--
In Fame's temple there is always a niche to be found for rich dunces,
importunate scoundrels or successful butchers of the human race. --
Zimmermam
Manoj Srivastava Systems Research Programmer, Project Pilgrim,
Phone: (413) 545-3918 A143B Lederle Graduate Research Center,
Fax: (413) 545-1249 University of Massachusetts, Amherst, MA 01003
<[EMAIL PROTECTED]> <URL:http://www.pilgrim.umass.edu/%7Esrivasta/>
