search for: libusb_strerror

On Jun 16, 2017, at 6:12 AM, Manuel Wolfshant <wolfy at nobugconsulting.ro> wrote: > > running autogen.sh was triggered automatically. but even if I do it explicitly, I still get: > + autoreconf -i > configure.ac:887: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body

...related to missing or too old tools mentioned by me in an earlier message ) - building against libsub 1.0 triggers the following 2 errors : nutdrv_qx-nutdrv_qx.o: In function `ippon_command': /builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/nutdrv_qx.c:679: undefined reference to `libusb_strerror' /builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/nutdrv_qx.c:692: undefined reference to `libusb_strerror' nutdrv_qx-nutdrv_qx.o: In function `fabula_command': /builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/nutdrv_qx.c:907: undefined reference to `libusb_str...

...apc-pdu-mib.o main.o dstate.o -Wl,-z -Wl,relro -Wl,-z -Wl,now ../common/.libs/libcommon.a ../common/.libs/libparseconf.a -L/usr/lib64 -lnetsnmp -lpthread nutdrv_qx-nutdrv_qx.o: In function `ippon_command': /builddir/build/BUILD/nut-libusb-1.0/drivers/nutdrv_qx.c:679: undefined reference to `libusb_strerror' /builddir/build/BUILD/nut-libusb-1.0/drivers/nutdrv_qx.c:692: undefined reference to `libusb_strerror' nutdrv_qx-nutdrv_qx.o: In function `fabula_command': /builddir/build/BUILD/nut-libusb-1.0/drivers/nutdrv_qx.c:907: undefined reference to `libusb_strerror' nutdrv_qx-nutdrv_qx.o...

...t; too old tools mentioned by me in an earlier message ) > - building against libsub 1.0 triggers the following 2 errors : > nutdrv_qx-nutdrv_qx.o: In function `ippon_command': > /builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/nutdrv_qx.c:679: > undefined reference to `libusb_strerror' > /builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/nutdrv_qx.c:692: > undefined reference to `libusb_strerror' > nutdrv_qx-nutdrv_qx.o: In function `fabula_command': > /builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/nutdrv_qx.c:907: > undefined...

Hi Manuel, 2017-06-14 15:16 GMT+02:00 Manuel Wolfshant <wolfy at nobugconsulting.ro>: > Hello > > > > On 06/14/2017 03:32 PM, Arnaud Quette wrote: > > > > On Jun 7, 2017, at 5:47 AM, Manuel Wolfshant <wolfy at nobugconsulting.ro> > wrote: > >> > >>> > If that matters, the OS is a fully updated CentOS 6.9 and this >>>

...n/libusb-config checking via /usr/bin/libusb-config... 0.1.12 found checking for libusb preferred version... 1.0.27 (libusb-1.0) checking for libusb cflags... -I/usr/include/libusb-1.0 checking for libusb ldflags... -lusb-1.0 checking for libusb.h... yes checking for libusb_init... yes checking for libusb_strerror... yes checking for libusb_kernel_driver_active... yes checking for libusb_set_auto_detach_kernel_driver... yes checking for libusb_detach_kernel_driver... yes checking for libusb_detach_kernel_driver_np... no checking for usb_detach_kernel_driver_np... no checking for libusb_get_port_number... yes...

...on where this is happening and did the following patch: diff --git a/drivers/libusb.c b/drivers/libusb.c index 50bfc7f..3eae478 100644 --- a/drivers/libusb.c +++ b/drivers/libusb.c @@ -353,7 +353,7 @@ static int libusb_open(usb_dev_handle **udevp, USBDevice_t *curDevice, USBDevice */ static int libusb_strerror(const int ret, const char *desc) { - if (ret > 0) { + if (ret >= 0) { return ret; } I've been running that patched version since April 16th, monitoring two UPSes (APC Back UPS XS 1000 and Cyber Power 1000AVRLCD) with no issues. -spc

...usr/bin/libusb-config... 0.1.12 found > checking for libusb preferred version... 1.0.27 (libusb-1.0) > checking for libusb cflags... -I/usr/include/libusb-1.0 > checking for libusb ldflags... -lusb-1.0 > checking for libusb.h... yes > checking for libusb_init... yes > checking for libusb_strerror... yes > checking for libusb_kernel_driver_active... yes > checking for libusb_set_auto_detach_kernel_driver... yes > checking for libusb_detach_kernel_driver... yes > checking for libusb_detach_kernel_driver_np... no > checking for usb_detach_kernel_driver_np... no > checking for...