On 20/07/13 18:47, Freddie Chopin wrote: > W dniu 20.07.2013 12:15, Paul Fertser pisze: >> Hi! >> >> I hope you're all right, you're absent for so long. > > So many things I'd like to do, so little time... > >> On Sat, Jul 20, 2013 at 10:28:50AM +0200, Freddie Chopin wrote: >>> The first issue is that configure does not detect libusb_error_name(), >>> but this is present in the lib, so the actual build fails: >> >> Can you please show your full config.log? > > The config.log is attached (gzipped). I think that the relevant part was > part of my previous message. > > I'm pretty certain that the problem is Windows-specific - the WINAPI > call (that's what LIBUSB_CALL is replaced with for Windows target) > changes the actual name of the function. But that's not only WINAPI - it > has to have one parameter, as this is embedded in the name too. WINAPI > calls are something like Linux system calls. I've explained that a bit > in the previous mail, with an example of test that compiles successfully. >
If i recall i had a similar issues building for i686 but not for x64. As a test can you put both the static and shared libusb-1.0 in your mingw lib directory. As an example /usr/i686-w64-mingw32/lib contains both libusb-1.0.a and libusb-1.0.dll.a. If i remove libusb-1.0.dll.a i also see this issue. Have not looked into it any further. Cheers Spen ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
