> I have already do the Makefile.am part, and it's create a good (I think,
> I hope) Makefile
> :(
> I don't understand because if I change my ./configure option line from
> ./configure --with-ft2232-lib=static --disable-werror (The one I use) to
> ./configure --enable-ft2232-lib --disable-werror (the one I don't want,
> because I need it to be have libftdi and libusb static)  It's work...
> Ho and I'm on Debian with libftdi 0.99

Okey. Then lets look at the command that actually fails:

 /bin/bash ../libtool --tag=CC   --mode=link gcc -std=gnu99  -g -O2
    -Wall -Wstrict-prototypes -Wformat-security -Wshadow -Wextra
    -Wno-unused-parameter -Wbad-function-cast -Wcast-align
    -Wredundant-decls   -o openocd main.o libopenocd.la
    ../jimtcl/libjim.a   -ldl
    libtool: link: gcc -std=gnu99 -g -O2 -Wall -Wstrict-prototypes
    -Wformat-security -Wshadow -Wextra -Wno-unused-parameter
    -Wbad-function-cast -Wcast-align -Wredundant-decls -o openocd
    main.o  ./.libs/libopenocd.a -lpthread -lrt ../jimtcl/libjim.a -ldl
    ./.libs/libopenocd.a(libhelper_la-options.o): In function `port_flag':

As far as I can tell, there is no -l for your libs. These lines should
have contained -lftdi -lusb and maybe some
-L/some/path/where/they/are/stored. The order might have something to say
(before or after libopenocd.a)

So for now, you could edit libopenocd.la by hand and add those (look for
-lrt or -ldl"). If that works, configure.ac and/or Makefile.am needs to be
fixed for static linking of ft2232.

.la files are libtool files which contains information about dependencies
etc for a library.


Stian Skjelstad


------------------------------------------------------------------------------
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
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to