checking for usleep ... yes
checking for vasprintf ... yes
checking for ". / guess-rev.sh" ... no
configure: Using: ftdichip.com library: / home/sebastiano/Scrivania/libftd2xx0.4.16_x86_64
checking for libftd2xx.a (linux) ... Found: / home/sebastiano/Scrivania/libftd2xx0.4.16_x86_64/static_lib/libftd2xx.a.0.4.16
checking Test: Build & Link with ftd2xx ... configure: error: Can not build & run test program using ftd2xx.lib
When running the ./configure scripts try having an ftd2xx device installed and plugged into your USB port that is using the same exact version of the ftd2xx drivers you are compiling with. Otherwise the check and test for ftd2xx.lib will fail and you will get an error like this:
checking for ftd2xx.lib exists (win32)... checking whether ftd2xx library works.
.. configure: error: Cannot build & run test program using ftd2xx.lib
On my first build attempt of OpenOCD I had never previously connected any FTD2xx devices to my computer. Based on the error message, I then connected my Olimex device and then installed the FTD2xx drivers. I left the Olimex device plugged in when I build OpenOCD and the build worked perfectly. I guess it was installing the FTD2xx drives that fixed my issue, not necessarily because I had the Olimex device plugged in at the time I was building OpenOCD. That’s good to know. Thanks.
ntfreak:
Hi,
you do not need to connect a device when running the configure script.
It only checks that the ftdi lib can be found and linked against.
Could you confirm the configure options you are using?