libusb-1.0 isn't backward compatible with 0.1, they are designed to install alongside each other. I stopped trying to get it to work on my Mac; I'm going to try a virtual machine (debian) today, and if that doesn't work I have an old computer that I can just install Ubuntu or something on.
Thanks for the advisement. Austin On Jul 19, 2010, at 7:05 AM, concordance-devel-requ...@lists.sourceforge.net wrote: > Date: Sun, 18 Jul 2010 21:17:51 +0200 > From: Phil Dibowitz <p...@ipom.com> > Subject: Re: [concordance-devel] OSX install problems with libusb > To: concordance-devel@lists.sourceforge.net > Message-ID: <4c43535f.2050...@ipom.com> > Content-Type: text/plain; charset="iso-8859-1" > > On 07/18/2010 08:57 PM, A Austin wrote: >> >> So, contrary to what I'm about to write, I'm not a complete idiot. >> >> Using the exact install instructions in libconcord/INSTALL.mac to install >> libusb (./configure --prefix=/usr -> make -> sudo make install) I get >> the same >> errors as I did in my previous mail. I did try to move libusb.h and the >> usb.h >> symlink to the /usr/include directory, which changed my configure output to: >> checking usb.h usability... yes, checking usb.h presence... yes, >> checking for >> usb.h... yes, checking for usb_init in -lusb... no, with a failure at that >> point. > > Right. As I said in my previous email, once you fix the headers, you'll need > to fix the libraries as well. > > It can find usb.h now (header), but I'm guessing it installed the libraries > in /usr/lib/libusb-1.0 as well, which is why it can't find the libraries > either. > > So your instinct here: > >> I did try a few other things including moving everything in >> /usr/lib/libusb-1.0 >> to /usr/lib and also tried to symlink libusb1.0.0.dylib to libusb.dylib >> but at >> that point I was mostly flailing helplessly. > > Was correct. These were the files it was looking for. Moving them should > have worked. > > HOWEVER, I've never tried building against libusb 1.0. Every major linux > distro is still shipping 0.1 by default, and that's what I've always linked > against. My guess here is that libusb 1.0 is putting itself in a > subdirectory to allow for both versions to be installed along side one > another. > >> I don't understand what 'usb_init in -lusb' means or what it's checking for, >> even after looking into the configure and Makefiles, but I'll attribute >> that to >> being a noob, so I don't really know how to fix this problem. > > That means it's compiling a small test program using "-lusb" (telling the > linker to link in libusb) and trying to call the usb_init() function. This > is how it can tell if the libusb on the system is there and functioning. ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
