On 13 July 2011 02:32, Andrew Leech <[email protected]> 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:
If the tarball was made using make dist then this would not be an issue. Infact most of your errors are because of this - jimtcl will also be included if this was a correct release. I have spent quite a while getting make dist to include all the jimtcl stuff, so unsure why it was not used. Hopefully we can correct this with the next rc. Cheers Spen _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
