Irrespective of 'usb' in the use flags, libgphoto2 compiles without usb support. Personally, I think it should by default support usb, but at least should do so with the usb use flag set. `gphoto2 --debug` shows the following: ... 0.005149 main(2): libgphoto2_port has been compiled with the following options: 0.005448 main(2): + gcc (C compiler used) 0.005705 main(2): + no USB (for USB cameras) ... Reproducible: Always Steps to Reproduce:
this took me quite a while to get working. i ended up just keep re-emerging libgphoto, gphoto2 and libusb till it worked. i wrote out some rudimentary instructions: http://formanonline.com/linux.htm
Thanks! I had already tried re-emerging libgphoto2, but that didn't work. So I tried libusb and libgphoto2 and it worked: emerge -uC libusb libgphoto2 && emerge -uU libusb libgphoto2 Even though this works, I don't think it's very intuitive. The libgphoto2 ebuild needs to be changed. If I have time I'll look into it.
What version of ebuilds? libgphoto2-2.1.1-r2 has a dependency on libusb-1.6 or higher already in the ebuild. As far as I know they always have.
I am using 2.1.1-r2, and I don't think the problem is with the dependency on libusb. I haven't looked into it in detail, but I think it's a compile flag that needs to be used on libgphoto2. I already had libusb installed when I installed libgphoto2 and `gphoto2 --debug` showed no USB support.
Might know what it is. Had it fail here trying to test for the libusb lib after passing the part looking for usb.h. The only real dependancy for libusb is libiconv in glibc. Maybe with the glibc update to Gentoo, libusb hasn't been recompiled and fails.? No way to catch it that I know of since configure doesn't return an error. Will pass on to the gphoto people.
temporary workaround: rm /usr/lib/libusb.so.0* and then try again.
oops assigned to the wrong person .. reassigning to myself
yup, remerging libusb seems to do the trick. here's before... root@tinygod libgphoto2-2.1.2 # libusb-config --version 0.1.7 root@tinygod libgphoto2-2.1.2 # ./configure | grep -i usb checking for libusb-config... /usr/bin/libusb-config ./configure: line 12725: ABOUT-NLS: command not found checking for libusb-config... /usr/bin/libusb-config checking usb.h usability... yes checking usb.h presence... yes checking for usb.h... yes checking for usb_busses in -lusb... no configure: WARNING: *** You need at least version 0.1.5 of the libusb library for USB support *** http://sourceforge.net/projects/libusb/ *** If you cannot find the appropriate version, try CVS . config.status: creating usb/Makefile USB support: no (available version too old) ?..?..?..would like to have. E.g. make sure that USB support is there if you ?..?..?..intend to use USB cameras with libgphoto2. and after remerging libusb... root@tinygod libgphoto2-2.1.2 # libusb-config --version 0.1.7 root@tinygod libgphoto2-2.1.2 # ./configure | grep -i usb checking for libusb-config... /usr/bin/libusb-config ./configure: line 12725: ABOUT-NLS: command not found checking for libusb-config... /usr/bin/libusb-config checking usb.h usability... yes checking usb.h presence... yes checking for usb.h... yes checking for usb_busses in -lusb... yes ./configure: line 13694: ABOUT-NLS: command not found config.status: creating usb/Makefile USB support: yes ?..?.. would like to have. E.g. make sure that USB support is there if you ?..?.. intend to use USB cameras with libgphoto2. the difference seems to be the usb_busses line. not really sure why. just another data point for those working on this. good luck.
its because usbutils is installing libusb.* which is conflicting with libusb (the package). this is what bug #25571 is on about. should be fixed soon (hopefully)
well, the usbutils and libusb conflict has just been fixed in ~x86 .. so that pretty much closes this bug off. i'm going to make libgphoto2 depend on both the new version of usbutils and libusb to make sure the changes are reflected when people update their libgphoto2
*** Bug 27883 has been marked as a duplicate of this bug. ***
*** Bug 28341 has been marked as a duplicate of this bug. ***
