if you emerge libusb1.7 and then libgphoto2-2.1.2 it fails to find the usb libs(for some unknown reason, it states it needs higher than 1.5 to work). I test this on x86 and found that the problem did not occur. I copied libusb1.7->libusb1.5 and lowered the libgphoto2 dependancy from libusb1.7 to libusb1.5 and everything linked and worked fine. Reproducible: Always Steps to Reproduce: 1.emerge libusb-1.7.ebuild 2.emerge libgphoto2-2.1.2.ebuild 3. Expected Results: libgphoto2 links against libusb1.7 It's kind of a crappy work around, but until the libgphoto people fix their autoconf scripts this is the only way i could get it to work.
I am having the same problem that you described, but I am on x86. Do you think you could provide more detail in your workaround? I would like to try what you tried, but I dont understand it. The only libusb libs I have are: bash-2.05b# ls /usr/lib/*usb* /usr/lib/libusb-0.1.so.4 /usr/lib/libusb.a /usr/lib/libusb.so /usr/lib/libusb.so.0.0.0 /usr/lib/libusb-0.1.so.4.3.0 /usr/lib/libusb.la /usr/lib/libusb.so.0 What should I copy from 1.7 to 1.5?
ok the details of the workaround are.... you must firts edit the libgphoto dependancies to say 'libusb>=1.5' instead of 1.7 . Then copy the libusb-1.7.ebuild, to libusb-1.5.ebuild in the portage tree. Finally you have to manually wget the file since none of the portage mirrors have it, this can be done by going to the sourceforge site, and finding the 1.7 download link, change the download url to 1.5 instead of 1.7 and wget it. The file should download fine put it in /usr/portage/distfiles. Then go back to the libusb directory in the portage tree and type 'ebuild libusb-1.5.ebuild digest'. This creates the digest files for the file you just downloaded. Now you can type 'emerge libusb-1.5.ebuild' Afterwards emerge libgphoto and everything should link properly.
that worked perfectly. thanks for the help.
*** This bug has been marked as a duplicate of 25845 ***
