On Fri, 26 Feb 2016 19:58:39 +0000 Steven Chamberlain <[email protected]> wrote:
[...] > > 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. > > Yes I agree. > > > Any idea about how to ping the developers? > > Usual procedure would be to file a PR at https://bugs.freebsd.org > but maybe I can do that for you. > I'd appreciate that, thanks, I don't use FreeBSD so I wouldn't be able to test the changes anyway. > In the meantime, if I put a stub function in kfreebsd's libusb that > only returns LIBUSB_ERROR_NOT_SUPPORTED - that would allow > kinect-audio-setup to compile - but would it likely break its > functionality? > That would be fine, libusb-1.0 itself returns LIBUSB_ERROR_NOT_SUPPORTED when the backend does not support detaching kernel drivers[1], and even the documentation states that[2]. [1] https://github.com/libusb/libusb/blob/master/libusb/core.c#L1915 [2] http://libusb.sourceforge.net/api-1.0/group__dev.html#ga1656d6b7272d4c82f842b20a834b1467 >From what I've seen, user programs usually call this function ignoring its return value to make the call transparent on systems that do not support detaching kernel drivers, so it _should_ be unlikely that your stub function will break the runtime behavior of current programs. Ciao ciao, Antonio -- Antonio Ospite http://ao2.it 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?
