On Sep 21, 2015, at 9:39 AM, Rob Groner <rgro...@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 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-includes=-I/usr/local/include 
--with-usb-libs=-L/usr/local/lib64

The key lines in the compilation testing:

configure:8062: gcc -o conftest /usr/local/include   conftest.c 
-L=/usr/local/lib64 >&5
/usr/local/include: file not recognized: Is a directory


_______________________________________________
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Reply via email to