On 13/07/2011, at 11:32 AM, Andrew Leech wrote: > On 11 July 2011 07:31, Jean-Christophe PLAGNIOL-VILLARD > <[email protected]> wrote: >>>> rc2 >>>> >>>> http://openocd.git.sourceforge.net/git/gitweb.cgi?p=openocd/openocd;a=snapshot;h=d4cd6f032015552f00bf4b5a90f25f5f958e9d9e;sf=tgz >>>> >>>> >>>> > I'm assuming some testing would be good :-) I'm just moving into a firmware > project again, so a good opportunity, recompiling from this tgz now. I'm been > compiling from git occasionally for a long time now, it's been a while since > starting from a fresh release. using Windows 7 x64, cygwin compiling. > > Couple of comments: > Firstly, the docs in the tarball could do with some updating, sorry I don't > have time to do it just now. > > README.Win32 mentions "The Cygwin/Win32 ZIP file contains a directory named > ftd2xx.win32". This doesn't exist, will it be included in a proper release > tarball, or are these referring to the ftdi files that can't be distributed > legally? > > Similarly the ./bootstrap command is only mentioned at the end of README, > while I'm guessing that this wont be needed in a release tarball, if anyone > who does need it tried to follow the readme linearly they'll run into > problems before finally finding this down the bottom, I feel it should > probably be mentioned earlier up. > > Again just a release tarball issue, but the tarball from above doesn't work > properly, it needs bootstrap run to get jimtcl etc, but I get: > $ ./bootstrap > + aclocal > + libtoolize --automake --copy > + autoconf > + autoheader > + automake --gnu --add-missing --copy > configure.in:20: installing `./compile' > configure.in:28: installing `./config.guess' > configure.in:28: installing `./config.sub' > configure.in:8: installing `./install-sh' > configure.in:8: installing `./missing' > doc/Makefile.am:1: installing `doc/mdate-sh' > doc/Makefile.am:1: installing `doc/texinfo.tex' > src/Makefile.am: installing `./depcomp' > Makefile.am: installing `./INSTALL' > Setting up submodules > fatal: Not a git repository (or any parent up to mount parent /cygdrive) > Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). > > It expects the openocd dir to be a git repository, but this tarball isn't. > Nasty workaround.... I copied .git from my existing openocd source folder > into the tarball folder and that got me jimtcl and the rest of the way > through bootstrap. > > I think README.Win32 should be updated regarding gcc options, mentioning that > using default gcc will result in cygwin dependency, or alternately install > cygwin packages for mingw and then specify the full mingw gcc name as per > below or CC="gcc-3 -mno-cygwin" (which I haven't tested recently): > Using: $ ./configure --enable-maintainer-mode --enable-ft2232_ftd2xx > --with-ftd2xx-win32-zipdir=../ftdi CC="i686-pc-mingw32-gcc" > > I also had problems with jimtcl and dos line ends, the configure scripts and > autosetup files didn't work, spitting some nasty errors because of dos line > ends... this took me a while to debug. Could bootstrap have it's git commands > for pulling jimtcl changed to ensure it doesn't save in dos mode? > Once I did a $ fromdos jimtcl/* and $ fromdos jimtcl/autosetup* configure > passed just fine. > > make completed with no issues. > Debugging a lpc3131 (ARM926EJ-S) with a ft2232 jtagkey compatible dongle then > works fine! > > Cheers, > Andrew
You are building with the wrong tarball. A release tarball is named something like openocd-0.5.0-dev.tar.gz and is built from the git repository with 'make dist' You should unpack this release tarball somewhere and just run ./configure You shouldn't be running bootstrap. In fact it doesn't exist in a proper release tarball. Cheers, Steve PS It's so easy to make one of these, I'm not sure why there is reluctance to do so. -- µWeb: Embedded Web Framework - http://uweb.workware.net.au/ WorkWare Systems Pty Ltd W: www.workware.net.au P: +61 434 921 300 E: [email protected] F: +61 7 3391 6002 _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
