On Thursday, September 26, 2002, at 07:29 PM, Justin C. Walker wrote: On Thursday, September 26, 2002, at 03:23 PM, Michael Cashwell wrote: Greetings all, I'm trying to be good and not include userland headers in my NKE. I'd think that was enlightened self-interest (since doing so would likely cause problems in your NKE and the kernel). Is that not a complete setup for doing NKEs? Do I need to download something else, possibly from the Darwin repository)? If so, what (and what tag) would ensure I get files compatible with Apple's released kernels? Roughly speaking, what you need to do is check out the appropriate version of the kernel (project 'xnu', with a tag "Apple-xxxx" matching what your kernel says (uname -a) in the form "xnu-xxxx"). Then use the headers from that kernel. Your best bet is to get the missing headers from there and put them in a convenient place, and reference them with an additional "-I" flag. If you are building for the system you are running on, it's OK to put them in the "proper" place. Actually, in this particular case, kern/lock.h is included in the Kernel.framework headers. The problem is more likely that Michael was looking for the header in /usr/include. It will not be there. It is a kernel-only header. If you want to look at the header, it will be in: /System/Library/Frameworks/Kernel.framework/Headers/kern/lock.h and the Kernel.framework will be included when you tell Project Builder that you are building a KEXT. --Jim _______________________________________________ darwin-kernel mailing list | darwin-kernel@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel Do not post admin requests to the list. They will be ignored.