On 25.06.2017 03:06, Roland Hieber wrote:
> Hmm, this seems to have happened before [0]. Are you by any chance
> building on Mac OS X? :) However, I remember I was running into the same
> error last week on my Debian machine at work, and I think I also
> switched to libftdi1, which solved it. Unfortunately, I cannot reproduce
> it now, 0.5.0 builds fine with libusb-1 and libftdi-0.20 on my current
> machine.

Ah, a bit more googling and it turns out that these errors seem to be
related to using a non-GNU libc. This has apparently been fixed in
libusb-1 [0], and Debian apparently also fix it in libusb-0.1 [1], which
explains why it works on my machine (but not why it didn't work on my
work machine…)

However, I'll stick to the argument that libusb1 and libftdi1 are
probably the better choices for the future :)

[0]: http://thread.gmane.org/gmane.comp.lib.libusb.devel.general/22400
[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=315165

 - Roland

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel

Reply via email to