Fair enough. What would be the best way to deal with the existing error with intr.h then? It persists in the src tree as well.
/usr/include/x86/intr.h:131: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'ipl_cookie_t' /usr/include/x86/intr.h:138: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'int' On Wed, May 26, 2010 at 12:37 PM, Jonathan A. Kollasch <[email protected]> wrote: > On Wed, May 26, 2010 at 12:10:44PM -0500, Matt Smith wrote: >> Hello, >> >> I'm working on porting the OpenAFS client over to NetBSD 5.0.2. In >> trying to compile the LKM for it, the files cpu.h and intr.h in >> /usr/include/x86/ are included. These headers include additional >> headers. The problem, however, is that a couple of the headers they >> try to include are not in /usr/include/x86. For example: >> >> /usr/include/x86/cpu.h includes /x86/via_padlock.h >> /usr/include/x86/intr.h includes /machine/pic.h >> >> Instead, these included headers are located in the src tree >> (/usr/src/sys/arch/x86/include). They can be linked in to satisfy the >> dependency, but intr.h errors out due to missing some expected >> characters. >> >> Does anyone know why these files would be missing from /usr/include? >> Additionally, why would non-compilable files be placed for use in >> /usr/include? > > I don't think we have yet bothered to support building 3rd-party kernel > modules without also having various parts of the src tree around. > > At least this was the case with Arla. I believe OpenAFS needs src > trees for OpenBSD and FreeBSD cache manager builds too. > > I could see it being hard to integrate, but using <bsd.kmodule.mk> > may make some things easier. > > Jonathan Kollasch > -- Matt Smith
