Steve Franks wrote:

Steve>>  [never used configure before, it is new to me]

1) Exactly how are you executing "./configure"? Are you specifying:  
--enable-ft2232_libftdi

By default: OpenOCD requires the use of --enable options, it does not 
automatically find things like UrJTAG.
By default: Those things are disabled.

steve>>  Here's the nutshell. I've gotten it to build fine on my system 
(yes,
steve>> we do have libusb and libftdi). The big thing is that I had to go
steve>> hack the makefiles manually after configure to add a
steve>> -I/usr/local/include to the build steps, and -L/usr/local/lib
steve>> to the linker in order to find libftdi.

2)  Question: Does GCC FreeBSD search: /usr/local/include automatically? 
yes or no.

That seems very strange, I have always thought of the host compiler 
always looking at /usr/local/include and /usr/local/lib.

See the output of "gcc -v  -Wl,--verbose  foo.c" look for this type of 
info in the output

 (A) - The "-I/usr/local/include" is automatic from GCC on Linux.

    #include "..." search starts here:
    #include <...> search starts here:
     /usr/local/include
     /usr/lib/gcc/i386-redhat-linux/4.1.2/include
     /usr/include
    End of search list.

(B) The "-L/usr/local/lib" is automatic from GCC on Linux
 
        SEARCH_DIR("/usr/i386-redhat-linux/lib");
        SEARCH_DIR("/usr/local/lib");
        SEARCH_DIR("/lib");
        SEARCH_DIR("/usr/lib");

Are these things *NOT* by default on FreeBSD? Seems strange.

-Duane.

_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to