search for: libusb

On Sep 15, 2015, at 9:31 PM, Charles Lepple <clepple at gmail.com> wrote: > >> Trying to track down the source of the problem, I checked Yast to make sure I had at least 0.1.8 version for libusb. I saw this (attached photo). Is it then actually using ?compat instead of the ?real? libusb? And is that a problem? > > You're right, both the -compat and real libusb packages will use the same libusb-0.1.so* name. I misspoke. The "real libusb" (0.1) and libusb-compat wil...

...list: http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser Also, please gzip any attached logs.] > Hello, > > I downloaded NUT ver 2.6.2 and tried it on my Linux development > board. when I configure and it notified me that "USB drivers > requested, but libusb not found." > Then I download libusb v1.0.8 and install it to my board, and re- > configure NUT, still "USB drivers requested, but libusb not found". > I look into config.log, and found that usb.h not found. > I tried Google and install libusb-compat. Then usb....

Hi Steve thanks for your answer. I follow your tutorial untill this instruction: wget "http://downloads.sourceforge.net/project/libusb/libusb-1.0/libusb- 1.0.18/libusb-1.0.18.tar.bz2? r=http%3A%2F%2Fwww.libusb.org%2F&ts=1404210716&use_mirror=softlayer-ams" -O libusb-1.0.18.tar.bz2 in my opiniono there are 2 " that are not needed and i when -O libusb- 1.0.18.tar.bz2 is not recognize from shell ( maybe because the...

...don't see anything more than I already thought I knew. It's as cryptic as configure itself. > > It does reference the line in the configure where the test for USB failed, but I'd already been looking in there. I can't make sense of the lines above that set "nut_have_libusb", as far as what they're looking for. Clearly somehow, that is supposed to be set to "yes". You have: ./configure --with-usb --with-dev --with-usb-includes=/usr/local/include --with-usb-libs=-L=/usr/local/lib64 I think you want: ./configure --with-usb --with-dev --with-usb-i...

...udo mkdir /usr/lib/scripts sudo mv acscripts-0.0.1.13 /usr/lib/scripts/acscripts #autoreconf from source wget http://sourceforge.net/projects/autoreconf/files/0.0.0.1/autoreconf-0.0.0.1.tar.bz2 tar xf autoreconf-0.0.0.1.tar.bz2 cd autoreconf-0.0.0.1 ./configure && sudo make install cd .. #libusb and libusb-compat from source wget "http://downloads.sourceforge.net/project/libusb/libusb-1.0/libusb-1.0.18/libusb-1.0.18.tar.bz2?r=http%3A%2F%2Fwww.libusb.org%2F&ts=1404210716&use_mirror=softlayer-ams" -O libusb-1.0.18.tar.bz2 tar -xjf libusb-1.0.18.tar.bz2 cd libusb-1.0.18 ./co...

...). Richard On Sun, Apr 5, 2015 at 3:34 AM Richard Flint <richard.flint at gmail.com> wrote: > Hi, > > I have to admit this sounds like it could screw up the system if not done > right - particularly because the solaris packaging system is unlikely to > allow me to remove the libusb package if many things are dependent on it. > > Are there any other options - e.g. doing something with the libusb that > ships with solaris - are we sure it doesn't support timeouts? > > I think I found some code relating to it here: > > https://java.net/projects/solaris-u...

...of the headers? if gcc -DHAVE_CONFIG_H -I. -I../../drivers -I../include -I../../include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/hal -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -DINET6 -O2 -D_REENTRANT -DNETSNMP_USE_INLINE -Wall -Dlinux -I. -I/usr/include -O -Wall -Wsign-compare -MT libusb.o -MD -MP -MF ".deps/libusb.Tpo" -c -o libusb.o ../../drivers/libusb.c; \ then mv -f ".deps/libusb.Tpo" ".deps/libusb.Po"; else rm -f ".deps/libusb.Tpo"; exit 1; fi ../../drivers/libusb.c:93: error: expected declaration specifiers or '...' before ...

...LD. . . is for the runtime dynamic linker. - Tim On 09/22/2015 03:48 PM, Rob Groner wrote: > Tim, > > Thanks for the help! No, I didn't already know that... I swear, the more time I spend at this, the less I seem to be understanding. > > I know that it had to be finding the libusb-compat I had just installed, because configure hadn't worked before that, and now it did. But finding useful version information seems to be almost impossible. > > Rob Groner > Software Engineer Level II > > RTD Embedded Technologies, Inc. > ISO 9001 and AS9100 Certified >...

...nt <richard.flint at gmail.com> wrote: > Again, apologies for my ignorance - are you suggesting that if the NUT application was built against openusb this would probably be fixed? Yes, that is my current theory. It's a little complicated in practice - openusb has a different API than libusb-0.1.x, but it supposedly includes a compatibility layer. If openusb works, I would not expect it to wait for more than 1 or 5 seconds when reading the reply. > If so I'm happy to give this a try - any idea how can I tell NUT to build against openusb instead of libusb? Not sure exactly, bu...

Rob - Just stepping in from the sidelines . . . with a few tidbits. Nut uses pkgconfig to find and identify stuff as part of it's build . . . So, depending on where your libusb install went, if it wasn't in the default "PKG_CONFIG_PATH" setting, it won't be found. Much like other shell variables, you can adjust that setting to find anything you like . . . IE PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/new/component;export PKG_CONFIG_PATH (or as appropriate fo...

So far, the systemd service unit is working perfectly. Halleluia! For reference, here are the libs associated with the usbhid-ups driver: rtd at linux-fnda:/etc/init.d> ldd /usr/local/ups/bin/usbhid-ups linux-vdso.so.1 (0x00007fffecd25000) libusb-0.1.so.4 => /usr/lib64/libusb-0.1.so.4 (0x00007ff3b841b000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007ff3b81fd000) libc.so.6 => /lib64/libc.so.6 (0x00007ff3b7e4e000) libusb-1.0.so.0 => /usr/lib64/libusb-1.0.so.0 (0x00007ff3b7c3e000) /lib64/ld-linu...

Well, I've spent a couple hours on this, unable to figure it out. I removed the libusb-compat-devel package using zypper. And I've downloaded, built, and installed libusb from sourceforge. But trying to configure nut now I get "USB drivers requested, but libusb not found", no matter what I put for --with-usb-libs. Continuing to flog away at it... Rob Groner Softwar...

Compiling against http://www.networkupstools.org/source/2.7/nut-2.7.4.tar.gz. I also have libusb-0.1-4 installed but no joy. On Mon, Mar 23, 2020 at 2:45 AM Jim Klimov <jimklimov at cos.ru> wrote: > On March 23, 2020 12:50:11 AM UTC, Tyler Montney <montneytyler at gmail.com> > wrote: > >Came across this in the process of troubleshooting: > > > https://alioth-...

Trying to install Canon printer driver package (rpm), I get a dependency error: libusb-1.0.so.0 is needed.... The version currently installed on my 5.9 system is libusb-0.1.12-6.el5 and, AFAIK (per yum), no upgrade to that is available. So question: Do higher centos versions have libusb-1.0.so ? (We could perform a quick inventory with: uname -r; rpm -q libusb Thanks.

On 12/17/2015 10:50 PM, hyouko at gmail.com wrote: > Can you try the nutdrv_qx driver with a debug level of 5 (i.e. five D > flags, nutdrv_qx -a upsname -DDDDD )? Attached is a logfile. -------------- next part -------------- A non-text attachment was scrubbed... Name: nutdrv_qx.log Type: text/x-log Size: 5727 bytes Desc: not available URL:

Thanks again Tim. I installed openSUSE from scratch, without installing libusb anything. I tried configure, and it failed because it couldn't find libusb. I used ldconfig to see what the system could see. It found 3 entries with "libusb" in them. I then built and installed the last update of libusb-0.1 (not libusb-compat or libusb-1.0). I tried configure, a...

...ard Flint <richard.flint at gmail.com> > wrote: > > Hi, > > Apologies for the many replies. I have found this documentation: > http://www.lehman.cuny.edu/cgi-bin/man-cgi?ugen+7 > > (I am using the ugen driver). > > > Right, AFAIK ugen is the kernel driver that libusb and openusb talk to > (/dev/usb/*). Updated diagram: > > upsc --- upsd --- nutdrv_qx --- libusb -+- ugen driver --- Solaris kernel > --- UPS > > Richard > > On Sun, Apr 5, 2015 at 3:34 AM Richard Flint <richard.flint at gmail.com> > wrote: > >> Hi, >>...

On Sun, Dec 14, 2014 at 07:22:01PM -0500, Mark LaPierre wrote: > On 12/14/14 07:29, ken wrote: > > uname -r; rpm -q libusb > > CentOS 6.6 says: > [mlapier at mushroom ~]$ uname -r; rpm -q libusb > 2.6.32-504.1.3.el6.i686 > libusb-0.1.12-23.el6.i686 CentOS 5 has: libusb-0.1.12 CentOS 6 has: libusb-0.1.12 libusb1-1.0.9 CentOS 7 has: libusb-0.1.4 libusbx-1.0.15 -- rgds Stephen

On Sep 22, 2015, at 3:47 PM, Rob Groner <rgroner at RTD.com> wrote: > So, here is what I think I know: > > NUT is using the libusb-1.0.20 library, by way of the libusb-compat layer. When I check the configure log, it says "libusb-0.1.12" I'm not sure why it says that, as in where it gets that value, as that version doesn't correspond to anything I installed. I see looking at the last version of libusb-0.1...

...15, at 10:45 PM, Richard Flint <richard.flint at gmail.com> wrote: > Hi, > > Apologies for the many replies. I have found this documentation: > http://www.lehman.cuny.edu/cgi-bin/man-cgi?ugen+7 > > (I am using the ugen driver). Right, AFAIK ugen is the kernel driver that libusb and openusb talk to (/dev/usb/*). Updated diagram: upsc --- upsd --- nutdrv_qx --- libusb -+- ugen driver --- Solaris kernel --- UPS > Richard > > On Sun, Apr 5, 2015 at 3:34 AM Richard Flint <richard.flint at gmail.com> wrote: > Hi, > > I have to admit this sounds like...