PDA

View Full Version : [ubuntu] 9.04 xconfigured self built question



FruitCase
June 15th, 2009, 12:23 PM
Hi list,

i am running into some stubborn error while trying to built my own configuration (warranty forfeit :). Can anybody help me out how to circumvent this error - i don't need video 4 linux, or qc_usb drivers, nor lirc etc., but am clearly stumbling in the dark as to what causes this error.


The error is this:

CC [M] ubuntu/qc-usb/qc-driver.o
In file included from ubuntu/qc-usb/qc-driver.c:46:
ubuntu/qc-usb/quickcam.h:509: error: field ‘vpic’ has incomplete type
ubuntu/qc-usb/quickcam.h:511: error: field ‘vwin’ has incomplete type
ubuntu/qc-usb/qc-driver.c: In function ‘qc_v4l_init’:
ubuntu/qc-usb/qc-driver.c:2285: error: ‘VIDEO_PALETTE_RGB24’ undeclared (first use in this function)
ubuntu/qc-usb/qc-driver.c:2285: error: (Each undeclared identifier is reported only once
ubuntu/qc-usb/qc-driver.c:2285: error: for each function it appears in.)
ubuntu/qc-usb/qc-driver.c: In function ‘qc_v4l_ioctl’:
ubuntu/qc-usb/qc-driver.c:2541: error: ‘VIDIOCGCAP’ undeclared (first use in this function)
ubuntu/qc-usb/qc-driver.c:2543: error: storage size of ‘b’ isn’t known
ubuntu/qc-usb/qc-driver.c:2543: warning: unused variable ‘b’
ubuntu/qc-usb/qc-driver.c:2563: error: ‘VIDIOCGCHAN’ undeclared (first use in this function)
ubuntu/qc-usb/qc-driver.c:2565: error: storage size of ‘v’ isn’t known
ubuntu/qc-usb/qc-driver.c:2577: error: ‘VIDEO_TYPE_CAMERA’ undeclared (first use in this function)
ubuntu/qc-usb/qc-driver.c:2565: warning: unused variable ‘v’
ubuntu/qc-usb/qc-driver.c:2584: error: ‘VIDIOCSCHAN’ undeclared (first use in this function)
ubuntu/qc-usb/qc-driver.c:2596: error: ‘VIDIOCGPICT’ undeclared (first use in this function)
ubuntu/qc-usb/qc-driver.c:2604: error: ‘VIDIOCSPICT’ undeclared (first use in this function)
ubuntu/qc-usb/qc-driver.c:2606: error: storage size of ‘p’ isn’t known
ubuntu/qc-usb/qc-driver.c:2606: warning: unused variable ‘p’
ubuntu/qc-usb/qc-driver.c:2630: error: ‘VIDIOCSWIN’ undeclared (first use in this function)
ubuntu/qc-usb/qc-driver.c:2632: error: storage size of ‘vw’ isn’t known
ubuntu/qc-usb/qc-driver.c:2632: warning: unused variable ‘vw’
ubuntu/qc-usb/qc-driver.c:2648: error: ‘VIDIOCGWIN’ undeclared (first use in this function)
ubuntu/qc-usb/qc-driver.c:2656: error: ‘VIDIOCGMBUF’ undeclared (first use in this function)
ubuntu/qc-usb/qc-driver.c:2658: error: storage size of ‘vm’ isn’t known
ubuntu/qc-usb/qc-driver.c:2658: warning: unused variable ‘vm’
ubuntu/qc-usb/qc-driver.c:2678: error: ‘VIDIOCMCAPTURE’ undeclared (first use in this function)
ubuntu/qc-usb/qc-driver.c:2680: error: storage size of ‘vm’ isn’t known
ubuntu/qc-usb/qc-driver.c:2680: warning: unused variable ‘vm’
ubuntu/qc-usb/qc-driver.c:2706: error: ‘VIDIOCSYNC’ undeclared (first use in this function)
ubuntu/qc-usb/qc-driver.c:2715: error: ‘VIDIOCGFBUF’ undeclared (first use in this function)
ubuntu/qc-usb/qc-driver.c:2717: error: storage size of ‘vb’ isn’t known
ubuntu/qc-usb/qc-driver.c:2717: warning: unused variable ‘vb’
ubuntu/qc-usb/qc-driver.c:2725: error: ‘VIDIOCKEY’ undeclared (first use in this function)
ubuntu/qc-usb/qc-driver.c:2731: error: ‘VIDIOCCAPTURE’ undeclared (first use in this function)
ubuntu/qc-usb/qc-driver.c:2737: error: ‘VIDIOCSFBUF’ undeclared (first use in this function)
ubuntu/qc-usb/qc-driver.c:2743: error: ‘VIDIOCGTUNER’ undeclared (first use in this function)
ubuntu/qc-usb/qc-driver.c:2744: error: ‘VIDIOCSTUNER’ undeclared (first use in this function)
ubuntu/qc-usb/qc-driver.c:2750: error: ‘VIDIOCGFREQ’ undeclared (first use in this function)
ubuntu/qc-usb/qc-driver.c:2751: error: ‘VIDIOCSFREQ’ undeclared (first use in this function)
ubuntu/qc-usb/qc-driver.c:2757: error: ‘VIDIOCGAUDIO’ undeclared (first use in this function)
ubuntu/qc-usb/qc-driver.c:2758: error: ‘VIDIOCSAUDIO’ undeclared (first use in this function)
make[3]: *** [ubuntu/qc-usb/qc-driver.o] Error 1
make[2]: *** [ubuntu/qc-usb] Error 2
make[1]: *** [ubuntu] Error 2
make[1]: Leaving directory `/usr/src/linux-source-2.6.28'
make: *** [debian/stamp/build/kernel] Error 2


What strikes me is that the xconfig method isn't very well adapted to helping ppl finding dependencies while presenting a myriad of choices. Is there a way normal humans can tell which choices have ramifications in the building process, like a 'aptitude' way of navigating the software stack of cards? It is nearly impossible to find solutions for building problems if the building configuration process is so primitive. Shouldn't be difficult to use dependency information. Is there a way to configure the kernel built using this kind of dependency information?

Thank you for helping me out

kind regards

FruitCase
June 15th, 2009, 03:57 PM
hi everybody,

solved the built problem by upgrading to the newest kernel and not modifying too much from oldconfig. Thanks for reading anyway ...