Gene Smith wrote, On 06/15/2009 10:12 PM: > Dean Glazeski wrote: >> You need to be careful about this. Sometimes, it isn't the best to >> stick locally build libraries in /usr/lib. For example, Fedora has a >> standard where locally built libraries go to /usr/local/lib while >> packaged libraries go to /usr/lib or /lib. In the case of Fedora, >> /usr/local/lib is in both the include and LD library paths, so there >> wouldn't be this problem. >> >> // Dean > > Good point. I changed the install of libftdi to prefix /usr/local as you > suggest but openOCD configure still can't find it. It found it OK when > installed at /usr . Unless I am doing something wrong...?? Is there a > configure option in openocd that I should be using? > >> Gene Smith wrote: >>> I did a default configure/make/make install on the latest libftdi >>> source tarball and it installed at /usr/share/. When I configured >>> openocd with --enable-ft2232_libftdi it complained about unable to >>> build and run the libftdi test program. By default, openocd configure >>> is expecting libftdi to be installed at /usr, not at /usr/share. (The >>> RPM install of libusb does put it at /usr and there is no problem with >>> it.) >>> >>> So when configuring libftdi, setting prefix=/usr fixes the problem. >>> >>> Possibly this should be added to the documentation. (There may be >>> other ways around this but for me this was the most straight forward.) >>> >>> -gene
Maybe this is what you were saying to do; it fixes it for me while letting me keep libftdi installed at its default, /usr/local: ./configure --enable-maintainer-mode --enable-jlink --enable-rlink --enable-ft2232_libftdi LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib Not sure why this is needed. If can't be fixed in configure it should at least be documented. _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
