Bug 81727 - new version : libusb-0.1.10
|
Bug#:
81727
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: All
|
Status: RESOLVED
|
Severity: enhancement
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: liquidx@gentoo.org
|
Reported By: casta@xwing.info
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: new version : libusb-0.1.10
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2005-02-12 05:43 0000
|
libusb need to be updated to 0.1.10 version
Bump of 0.1.8 ebuild removing the amd64 fPIC patch work for me (on ~x86)
from the libusb website:
The current stable version of libusb is 0.1.10a. This release fixes a variety of bugs, some of which are important. It is highly reccomended to use this version.
eradicator, are you planning to take over maintaining this? i was about to bump
this after i did some testing. but if you want to take over maintaining this,
then please let me know.
It's late here, so please excuse my taking this bug BEFORE sending you email...
I was just about to send you one, honest ;). It looks like kdebase doesn't
like 0.1.8 of libusb (atleast not here on amd64), so it needs some bumping. I
was going to take care of this since I'm testing it right now, but if you're on
it already, then by all means by my guest... it is your package after all... =)
Also, I think the -fPIC stuff should get the boot as libtool should be smart
enough to handle it correctly on amd64, and globally adding it to CFLAGS as is
done here results in PIC code ending up in a static lib. I realize this was
done to "fix" libgphoto, but this hack is unacceptable and libgphoto is the
culprit that needs to be fixed to work properly with libusb.
in portage and fpic patch removed. i'll prob have to go get an account on the
amd64 dev boxes to keep up with all these problems ;) thanks!