In message <[EMAIL PROTECTED]> Assar Westerlund writes:
: Warner Losh <[EMAIL PROTECTED]> writes:
: > In message <[EMAIL PROTECTED]> Assar Westerlund writes:
: > : The problem is that the source files are hidden in the kernel source
: > : directory and not installed.  Where should vnode_if.{src,pl} get
: > : installed?  It seems much simpler just to install vnode_if.h in
: > : /usr/include/sys.  Patch appended.
: > 
: > No.  
: > We don't install kenrel internal files.
: But it's not kernel internal.  It's used by modules/KLDs ?  Where
: should these expect to find it?


: > Use SYSDIR instead.
: I'm not sure what you mean by this?  Should vnode_if.h just reside in
: /sys/sys and be used from there or what?

No.  I mean that you need to have a kernel in $SYSDIR (or in /sys or
/usr/src) and that vnode_if.h will get built in '.'.

: > : + ${INSTALL} -C -o ${BINOWN} -g ${BINGRP} -m 444 \
: > : +         ${.OBJDIR}/vnode_if.h \
: > : +         ${DESTDIR}/usr/include/sys
: > 
: > I object to this part of the patch.  We shouldn't install this file.
: > It isn't needed by anything outside of the kernel/drivers.
: Well, depends on your point of view if that's outside kernel/drivers,
: but it's sure used by modules/KLDs.

No.  That's part of the kernel, for the purposes of this discussion.
It isn't used by userland at all.  It should be build by the kld
system, and if it isn't, then it is a bug.  Go look at
sys/modules/msdos/Makefile for an example of how it is supposed to

: > For drivers, it should be built automatically as part of the modules
: > build system ala the *_if.m stuff.
: Where are these files installed so that they can be used by
: third-party KLDs?

They aren't installed.  You must have a kernel tree to build the kld.
Just add vnode_if.h to your SRCS and the rest happens automatically
via  It works great.  I do it all the time.  In fact, I
added SYSDIR support to at Timing Solutions so that we
could compile our drivers outside of the tree.

There are lots of generated files like this that aren't installed, nor
should they be.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to