similar to: ./configure excludes USB drivers and documentation

[Andrew: please subscribe to the nut-upsuser 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

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

For fun, if you want to see where the system thinks it is linking a library from, you can use "ldconfig -p" and it will give you a path to all known libraries that it can find. If you have one loaded, and it can't find it (odd directory, etc.) you can always amend "LD_LIBRARY_PATH" the same way as PKG_CONFIG_PATH I mentioned earlier . . . . PKG . . . is for the build

Hello I am trying to install Oblivion on Fedora 16 64-bit but am having problems with the install sheild crashing. I have read that this is because of the 64 bit wine so I am trying to build an older version of wine from source. However I am having problems with this aswell. I suspect that this is because of the 64-bit OS aswell. the reason I say this is that it appears 'make' is still

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

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, and it ran without

I just upgraded the FreeBSD buildbot machine from 6.4 to 8.0, and I ran across some interesting differences. The libusb API that we use (0.1) is available in /usr/include/usb.h and /usr/lib/libusb.* as before, but it seems to be the compatibility layer from libusb 1.0. However, it doesn't include the libusb-config binary. This is from the 'ports' Makefile for NUT: ########## - -

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

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: > > >

On Sep 21, 2015, at 9:39 AM, Rob Groner <rgroner at RTD.com> wrote: > > I didn't think to look for a log (attached), but now looking in it, I 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

Ok, I tried this from scratch on a fresh 2.7.2 directory. I followed the web instructions, specifically: + I generated the new subdriver for my UPS (rtd-hid.*) based on PATH info. + I put them in the drivers subdir + I added the include line (#include rtd-hid.h) in usbhid-ups.c (specifically in the #ifndef SHUT_MODE section) + I added &rtd_subdriver, to the subdriver_list in usbhid-ups.c

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 >>>

Hi, I got a problem. I have the libusb drivers already, why does it still not find? The error is shown below. Thx. configure: error: "USB drivers requested, but libusb not found." [root at andy nut-2.7.4]# yum install libusb Loaded plugins: langpacks, presto, refresh-packagekit Package 1:libusb-0.1.3-11.fc18.i686 already installed and latest version Nothing to do [root at andy

On 06/15/2017 04:32 PM, Arnaud Quette wrote: Hello > > .... still no reply from them ... > > is the guy you contacted Paul Henri? I wrote to a generic alias ( Ro-PQSupport ). Got a reply from a fellow Romanian who also CC:ed something looking like a list (List-EGPQCO-BUCRO-PQ ). I replied to both of them 5 days ago, received nothing since. > >>> Would you also

I've used NUT successfully for monitoring many different brands of UPS, but this one has me stumped. It has the same manufacturer ID and Product ID as older supported MGE-type Eaton UPS's, but has trouble talking. I tried Ubuntu's repo NUT, and it logs a Connecting to UPS message every few seconds forever, but never really succeeds (or says it fails). Different failure mode after

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 Software

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

Hi Charles, thanks for the clarification on the libusb. that indeed does work to get the value in ./configure. I've tried installing a .deb sudo dpkg -i nut_2.7.4-5_all.deb (Reading database ... 103447 files and directories currently installed.) Preparing to replace nut 2.6.4-2.3+deb7u1 (using nut_2.7.4-5_all.deb) ... Unpacking replacement nut ... Setting up nut (2.7.4-5) ... which

Thanks Charles, you were right about that. Here is what I tried...I installed openSUSE 13.1 from scratch (which means no libusb). I then took libusb-1.0 from the sourceforge site and built and installed it. Still it got the "cannot find libusb" error. So, looking at the sourceforge site, is see it mention that to work with the older libusb-0.1, you had to use libusb-compat-0.1.5.

Came across this in the process of troubleshooting: https://alioth-lists.debian.net/pipermail/nut-upsuser/2011-November/007249.html My whole reason for compiling from source is to add SSL support (as it doesn't seem available through the package manager). Apt list shows these installed: libusb-1.0-0-dev/stable,now 2:1.0.22-2 armhf [installed] libusb-1.0-0/stable,now 2:1.0.22-2 armhf