Splitting kernel headers and deprecating __KERNEL__
Quoted 10 lines · Alexander Stohr
Quoted 3 lines
Quoted 2 lines · Matthew Wilcox
Indeed. We could also make this transparent to userspace by using a script to copy the user-* headers to
/usr/include. Something like this:some administrator would like to only create symlinks for saving disk space.
others would like a true "install" with copying files so that they can delete the kernel sources anytime they do want.
for me i would install all those kernel realted files into the well known /lib/modules/<kernel-version>.
IMHO the script should let you install the headers wherever you like. In particular, in crosstool, I would like to install the headers somewhere like /opt/crosstool/$TARGET/include rather than /usr/include.
- Dan
Signature · 1 line
Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html
Quoted 8 lines · Dan Kegel
Quoted 3 lines
for me i would install all those kernel realted files into the well known /lib/modules/<kernel-version>.
IMHO the script should let you install the headers wherever you like. In particular, in crosstool, I would like to install the headers somewhere like
/opt/crosstool/$TARGET/includerather than/usr/include.
Agreed and trivial to do.
One should recall that for current kernel the following path is valid:/lib/modules/uname -r/source/include/*
This is valid for 2.6.7 or something.
Sam