What to do? I'm trying to build for stlink, and 'make' is spitting up. This is with the tar.bz2 file that I just downloaded from Sourceforge an hour or two ago.
To put the last first, if after I lose patience with the stuff below I do a 'make clean', then do ./configure --enable-ft2232_libftdi then do make everything works fine, even if it's already messed up. But (obviously) I don't have stlink support. But if I want to build for the stlink, there appears to be some dependency clashes going on -- I need libusb-0.1 to compile, but then I can't link. Whuzzup? I'm easily confused, and I've certainly been pushed there with this! Here's the details: Without libusb-0.1-4 installed I do: ./configure --enable-ft2232_libftdi --enable-stlink then: make I get: ti_icdi_usb.c:36:31: fatal error: libusb-1.0/libusb.h: No such file or directory If I then install libusb-0.1-4 and rebuild, I get ./.libs/libopenocd.a(ti_icdi_usb.o): In function `icdi_send_packet': /home/tim/Distributions/openocd-0.7.0/src/jtag/drivers/ti_icdi_usb.c:154: undefined reference to `libusb_bulk_transfer' /home/tim/Distributions/openocd-0.7.0/src/jtag/drivers/ti_icdi_usb.c:162: undefined reference to `libusb_bulk_transfer' /home/tim/Distributions/openocd-0.7.0/src/jtag/drivers/ti_icdi_usb.c:193: undefined reference to `libusb_bulk_transfer' ./.libs/libopenocd.a(ti_icdi_usb.o): In function `icdi_usb_close': /home/tim/Distributions/openocd-0.7.0/src/jtag/drivers/ti_icdi_usb.c:617: undefined reference to `libusb_close' /home/tim/Distributions/openocd-0.7.0/src/jtag/drivers/ti_icdi_usb.c:620: undefined reference to `libusb_exit' ./.libs/libopenocd.a(ti_icdi_usb.o): In function `icdi_usb_open': /home/tim/Distributions/openocd-0.7.0/src/jtag/drivers/ti_icdi_usb.c:650: undefined reference to `libusb_init' /home/tim/Distributions/openocd-0.7.0/src/jtag/drivers/ti_icdi_usb.c:655: undefined reference to `libusb_open_device_with_vid_pid' /home/tim/Distributions/openocd-0.7.0/src/jtag/drivers/ti_icdi_usb.c:661: undefined reference to `libusb_claim_interface' collect2: ld returned 1 exit status -- Tim Wescott www.wescottdesign.com Control & Communications systems, circuit & software design. ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
