Re: [Dav-linuxfs] Problem using davfs.o

[Grant B. <gra...@sv...>]

* Sung Kim <hu...@ke...> [011031 23:34]:
> I guess the problem is "-k6" in your kernel.
> If you could rebuild whole kernel, it would be work.

Thanks for your prompt response and I do appreciate your efforts.  I'm
still looking forward to trying davfs for the first time.  However, to
put this bluntly, I think you are wrong.

The force option of `insmod -f` should take care of the mismatch of
kernel version.  I highly doubt this is the cause of the problem.

I did update my system.  I updated it to the latest pre-packaged version
of the kernel for my Debian system along with the source, 2.4.12.  I
have no need or desire to compile from scratch, nor do many users of
GNU/Linux systems I suspect.  Unfortunately, even after I got a totally
fresh copy of davfs from CVS and I run the following commands manually
`configure --with-ssl --with-kernel=/usr/src/kernel-2.4.12` ; `make` ;
`su` ; `make install` I still get the error message that it's compiled
for 2.4.8!  I don't understand this at all, but I'm willing to learn.  I
still doubt that the kernel version is the cause of the problem.

Please note this part of my last message:

> /lib/modules/2.4.8-k6/kernel/fs/davfs/davfs.o: unresolved symbol kernel_flag

I get a similar error now.  I think this is the cause of the problem.
Again, this is over my head but I am willing to learn.  What's the first
step in finding more about this symbol?  Checking the kernel for
kernel_flag with `nm -s` or something?

I now also get another warning: 

> /lib/modules/2.4.12-k6/kernel/fs/davfs/davfs.o: Note: modules 
> without a GPL compatible license cannot use GPLONLY_ symbols

I have been reading over the last few weeks on lwn.net about some of the
legal issues regarding linking to GPL code and the kernel and modules.
I am guessing it must be a result of changes in the kernel related to
those issues being discussed.

And I am now getting this error multiple times during compile:

> gcc   -c -o proc.o -O3 -Wall -DMODULE -D__KERNEL__ -DLINUX
> -fomit-frame-pointer -I/usr/src/kernel-source-2.4.12/include proc.c
> In file included from /usr/include/asm/smplock.h:6, from
>  /usr/src/kernel-source-2.4.12/include/linux/smp_lock.h:16, from proc.c:20:
>  /usr/src/kernel-source-2.4.12/include/linux/interrupt.h:77: warning: 
>     `__cpu_raise_softirq' redefined
>  /usr/include/asm/softirq.h:48: warning: this is the location of the 
>     previous definition

And when I got a fresh copy of the davfs from CVS, I again had to change
the configure script to check for .../include/kernel/kernel.h instead of
.../include/kernel/version.h in two places to get it to recognize my
kernel directory when running `configure --with-ssl
--with-kernel=/usr/src/kernel-2.4.12`.  There is no longer a version.h
at that location in the kernel source.

These errors seem to point to changes in the kernel module interfaces
that davfs is using:  the configure script, the unresolved kernel_flag
symbol, the GPLONLY warning & softirq.h warning.  Is this correct?

Regards,

--
-- Grant Bowman                                   <gra...@sv...>