build -->/usr/src/linux

* $ from [email protected] at "10-Apr: 6:42pm" | sed "1,$s/^/* /" *
*
* richard offer wrote:
* > * > uname does not always provide useful information (cross compiling). Even
* > * > if you're building the same ISA, you maybe in a chroot'ed environment.
* > * >
* > * > Can we please not assume that everybody only ever builds native...
* > *
* > * Nobody is assuming that. If you're hard enough to do a cross compile,
* > * you can build external modules using "make KERNEL_RELEASE=2.4.2
* > * KERNEL_SOURCE=/home/jamie/cross_compiling/kernel ARCH=mips64" or
* > * whatever.
* >
* > Applications make that assumption all the time.
* >
* > Yes, this is the kernel mail list, but applications use kernel services. By
* > tacitly agreeing that you get the kernel headers from /lib/modules/`uname
* > -r`/build/include that's what people will code into their makefiles. *
* _Applications_ should not use kernel headers at all. For ioctls, they
* should ship with copies of the definitions they need. That's been made
* clear as crystal many times on this list, and it should be in the FAQ if
* it isn't already.

What if your application contains some user code and a kernel module ?

Want an obvious example ? X.

*
* > Saying "oh, but applications should do that" isn't much of a argument,
* > as there isn't a better way of working out where a set of kernel
* > headers are.

s/should/shouldn't/

*
* -- Jamie
*

richard.

-----------------------------------------------------------------------
Richard Offer Technical Lead, Trust Technology.
"Specialization is for insects" __________________________________________http://reality.sgi.com/offer/