[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#815265: kinect-audio-setup: FTBFS on kfreebsd: implicit declaration of function 'libusb_set_auto_detach_kernel_driver'

On Sun, 21 Feb 2016 00:38:06 +0000
Steven Chamberlain <steven@pyro.eu.org> wrote:

> Hello,

Hi Steven,

> Antonio Ospite wrote:
> > libusb_set_auto_detach_kernel_driver() is available in libusb-1.0 since
> > v1.0.16 dated 2013-07-11, according
> > to /usr/share/doc/libusb-1.0-0/changelog.gz
> > 
> > I see that the kfreebsd ports use a compatible library named libusb2,
> > where can I find more info about it?
> > 
> > Can the libusb-1.0 library from http://libusb.info/ be used at all on
> > kfreebsd?
> That does not support the kernel of FreeBSD.  So FreeBSD had its own
> implementation of the libusb 0.1 and 1.0 APIs.  FreeBSD just calls it
> libusb:
> http://www.freebsd.org/cgi/man.cgi?query=libusb&apropos=0&sektion=3&manpath=FreeBSD+10.2-RELEASE&arch=default&format=html


> The Debian package is called libusb2-dev for some reason I don't
> know(?);  the library is in a package called libusb3 to match the
> current SONAME which is .3
> The latest usb.h upstream is unchanged since 2013-03-13 so it has no
> libusb_set_auto_detach_kernel_driver:
> http://svnweb.freebsd.org/base/head/lib/libusb/usb.h?view=markup

This is the libusb0.1 compat header, the one for libusb-1.0 seems to be

Anyway, I think the proper, long-term solution would be to have the
library updated to match a more recent libusb-1.0 version, rather than
patching every single program.

Any idea about how to ping the developers?


Antonio Ospite

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?

Reply to: