error: unknown field ‘owner’

2006-03-19
2013-06-03
  • Nobody/Anonymous

    G'day

    I'm getting this error on line 3031
    Any suggestions?

    [cheeseness@localhost qc-usb-0.6.3]$ make all
    make -C "/lib/modules/2.6.15-1.2041_FC5/build" SUBDIRS="/home/cheeseness/qc-usb-0.6.3" modules V=1 USER_OPT=""
    make[1]: Entering directory `/usr/src/kernels/2.6.15-1.2041_FC5-i686'
    mkdir -p /home/cheeseness/qc-usb-0.6.3/.tmp_versions
    make -f scripts/Makefile.build obj=/home/cheeseness/qc-usb-0.6.3
      gcc -m32 -Wp,-MD,/home/cheeseness/qc-usb-0.6.3/.qc-driver.o.d  -nostdinc -isystem /usr/lib/gcc/i386-redhat-linux/4.1.0/include -D__KERNEL__ -Iinclude  -include include/linux/autoconf.h -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -ffreestanding -Os     -fomit-frame-pointer -g -pipe -msoft-float -fno-builtin-sprintf -fno-builtin-log2 -fno-builtin-puts  -mpreferred-stack-boundary=2  -march=i686 -mtune=pentium4 -mregparm=3 -Iinclude/asm-i386/mach-default -Wdeclaration-after-statement -Wno-pointer-sign -DNOKERNEL   -DMODULE -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(qc_driver)"  -D"KBUILD_MODNAME=KBUILD_STR(quickcam)" -c -o /home/cheeseness/qc-usb-0.6.3/.tmp_qc-driver.o /home/cheeseness/qc-usb-0.6.3/qc-driver.c
    /home/cheeseness/qc-usb-0.6.3/qc-driver.c:3031: error: unknown field ‘owner’ specified in initializer
    /home/cheeseness/qc-usb-0.6.3/qc-driver.c:3031: warning: initialization from incompatible pointer type
    make[2]: *** [/home/cheeseness/qc-usb-0.6.3/qc-driver.o] Error 1
    make[1]: *** [_module_/home/cheeseness/qc-usb-0.6.3] Error 2
    make[1]: Leaving directory `/usr/src/kernels/2.6.15-1.2041_FC5-i686'
    make: *** [quickcam.ko] Error 2

     
    • Nobody/Anonymous

      I'm getting the very same error after upgrading to kernel 2.6.16. Maybe it is relatet to a change in the usb driver model. I'll look into that.

       
    • Nobody/Anonymous

      I get it too... :(

       
      • j-d-williams

        j-d-williams - 2006-04-15

        If you look in the patches there is a patch for this and other things.

         

Log in to post a comment.