On Sat, May 5, 2012 at 8:12 PM, Xiaofan Chen <[email protected]> wrote:
> It seems to me that the latest git is almost working right out
> of the box under Mac OS  X Lion. But there is still
> a minor issue with libusb-1.0 dylib name in the last step.
> BTW, I am using homebrew.
>
> libtool: link: gcc -std=gnu99 -g -O2
> -I/usr/local/Cellar/open-ocd/HEAD/include -Wall -Wstrict-prototypes
> -Wformat-security -Wshadow -Wextra -Wno-unused-parameter
> -Wbad-function-cast -Wcast-align -Wredundant-decls -o openocd main.o
> -L/usr/local/Cellar/open-ocd/HEAD/lib ./.libs/libopenocd.a
> /usr/local/lib/libusb-1.0.0.0.0.dylib ../jimtcl/libjim.a -lftdi -lusb
> -pthread
> i686-apple-darwin11-llvm-gcc-4.2:
> /usr/local/lib/libusb-1.0.0.0.0.dylib: No such file or directory
> make[4]: [openocd] Error 1 (ignored)
>
> A dirty fix is to to this.
> cd /usr/local/lib/
> ln -sf libusb-1.0.0.dylib libusb-1.0.0.0.0.dylib
>
> But I am not so sure what is the proper fix.
>

BTW, my configure script is like this.

LDFLAGS="-L/usr/local/lib -lusb-1.0" ../configure
--enable-maintainer-mode --disable-option-checking
--prefix=/usr/local/Cellar/open-ocd/HEAD --enable-jlink
--enable-ft2232_libftdi --enable-stlink --disable-werror
--disable-shared

--disable-option-checking was needed to sort out jimtcl problem. But
I just checked it is actually not needed now -- remove it and it
will still work,

-- 
Xiaofan

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to