Essentially, you should compile this module in the modules directory of
the kernel source. This will solve your problems in the easiest manner.
sorry for short answer.. driving all night back from HAL sleep.
andrew
On Sun, 12 Aug 2001, Rohit Grover wrote:
:Hello,
:
:I am writing a module
Rohit Grover wrote:
>
> On Sun, 12 Aug 2001, Dima Dorfman wrote:
> > Rohit Grover <[EMAIL PROTECTED]> writes:
> > > Interestingly, when I executed the command 'make depend',
> > > vnode_if.h was correctly created for me. I'd like to know why I don't
> > > need to do a 'make depend' for modules l
On Sun, 12 Aug 2001, Dima Dorfman wrote:
> Rohit Grover <[EMAIL PROTECTED]> writes:
> > Interestingly, when I executed the command 'make depend',
> > vnode_if.h was correctly created for me. I'd like to know why I don't
> > need to do a 'make depend' for modules like 'vn' or 'nfs' before
> > buil
Rohit Grover <[EMAIL PROTECTED]> writes:
> Interestingly, when I executed the command 'make depend',
> vnode_if.h was correctly created for me. I'd like to know why I don't
> need to do a 'make depend' for modules like 'vn' or 'nfs' before
> building them.
Perhaps because it was done before? C
Hello,
I am writing a module which needs to include 'sys/vnode.h'. vnode.h
tries to include vnode_if.h. I checked the Makefiles of some other
modules requiring vnode.h (eg. 'vn', 'nfs') and discovered that they
add vnode_if.h to to the variable 'SRCS'. This automagically generates
vnode_if.h in t
5 matches
Mail list logo