Andrew Leech wrote: > Again just a release tarball issue, but the tarball from above doesn't work > properly, it needs bootstrap run to get jimtcl etc
In particular for a release it's really really important that the two separate packages (OpenOCD and jimtcl) are *two separate packages*. The tricks that autobuild jimtcl are convenient for random perusal but does not very nice packaging make. > 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" CC should basically *never* be used. --host=i686-pc-mingw32 should be given to configure in this case, with no environment variables. > I also had problems with jimtcl and dos line ends, the configure > scripts and autosetup files didn't work Nod. For unknown reason at least configure absolutely must have LF only line endings. > Could bootstrap have it's git commands for pulling jimtcl changed > to ensure it doesn't save in dos mode? Rather difficult. Unsure how that would be done if at all. What could be done is to add eol=lf in .gitattributes for the files that need it. > Debugging a lpc3131 (ARM926EJ-S) with a ft2232 jtagkey compatible > dongle then works fine! Thanks for writing up the build issues and testing! //Peter _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
