On Tue, Dec 30, 2008 at 1:32 PM, Theodore A. Roth <[email protected]> wrote: > On Tue, Dec 30, 2008 at 12:02 PM, Duane Ellis <[email protected]> wrote: >> Ted> The test in configure.in is testing for linkage against a function >> Ted> that openocd is not even using. In my opion, that makes the test is >> Ted> broken. >> >> Be that as it may - and I generally agree with you - Version number hell >> sucks. None of us have means (and time, energy, etc) to go backwards and >> test permutations from Version Number Hell. >> >> But - as it stands now - the Win32 version I believe - requires at least >> 0.12 etc.. See the "CONTRIB" folder for info about this. So what are we to >> do? >> >> This entire problem is - interesting - and painful. as I pointed out in my >> original mail that Steve Franks quoted.. >> >> duane >> I wonder how many other bumps we will find :-( >> >> Our goal (putting blinders on and being 100% totally openocd centric) - is >> to get to a release 1.0 milestone. >> >> Having FreeBSD + MAC + WINDOWS + LINUX = all supported @ 1.0 is a great >> thing. > > It appears that FreeBSD uses 0.10 also. > > http://www.freebsd.org/cgi/ports.cgi?query=libftdi&stype=all > > Thus, no amount of tweaking of CFLAGS and/or configure options will > allow that test to pass. My patch should allow Steve to get openocd to > get past the configure stage on FreeBSD (assuming that > /usr/local/include is in his header search path and /usr/local/lib in > the lib search path). > > Ted Roth >
> Are you specifying: --enable-ft2232_libftdi If you don't, it builds fine, but somewhat pointlessly (who has a parallel port these days? I've got alot of old dongles to give away ;) I think Ted's nailed the issue. This neatly explains why urjtag builds fine with libftdi-0.10, and OOCD doesn't, it wasn't really a make issue at all - configure wasn't placing the right data in the makefiles since the test failed. As an aside, I can vouch that OOCD does appear to run on top of libftdi-0.10, since I've been using it that way (with my make tweaks) for several months. It's about to be a moot issue, apparently, since I hear we'll (FreeBSD) be bumping to libftdi-0.14 this month, so don't do to much work on my account, now that we know the problem isn't what I thought. Steve _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
