Date: Wed, 06 Mar 2002 09:02:27 -0700 (MST) From: "M. Warner Losh" <imp@village.org> To: rizzo@icir.org Cc: arch@FreeBSD.ORG Subject: Re: do we need full kernel sources to compile loadable modules ? Message-ID: <20020306.090227.127359201.imp@village.org> In-Reply-To: <20020305134932.A79697@iguana.icir.org> References: <20020305134932.A79697@iguana.icir.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20020305134932.A79697@iguana.icir.org>
Luigi Rizzo <rizzo@icir.org> writes:
: Plain and simple... I thought one could compile a kernel extension
: (foo.ko) without full kernel sources, as the various include files
: describing kernel interfaces and data structures are installed in
: various places under /usr/include .
: This seems to work fine in many cases.
But fails in most cases.
: Turns out, however, that at least one thing (namely vnode_if.h) is not
: there, and it needs to be reconstructed using sys/kern/vnode_if.{pl,src}
Yes.
: So i wonder:
:
: + is it a desirable goal that one can compile kernel extensions without
: requiring a full kernel source tree ?
No.
: + if so, shouldn't we make sure that, as part of the creation of
: /usr/include, a copy of vnode_if.h is generated somewhere (maybe
: in /usr/include/sys or wherever is more appropriate) ?
There's too many of these files. *_if.h from newbus makes this hard.
: + are there other header files (and maybe objects, e.g. there is also
: a vnode_if.o) which have similar problems ?
There are. the *if.h files are the tip of the iceburg last time I
tried it.
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020306.090227.127359201.imp>