On Wed, Aug 10, 2011 at 11:44 AM, Steve Bennett <ste...@workware.net.au> wrote: > On 10/08/2011, at 9:43 AM, Xiaofan Chen wrote: >> It was not up to date but very close. Anyway, I just updated it and >> the issue is still there with the release zip file. I will try the git >> tree later. >> >> === configuring in jimtcl >> (/cygdrive/d/work/openocd/openocd-0.5.0/build_mingw_cr >> oss/jimtcl) >> configure: running /bin/sh ../../jimtcl/configure.gnu >> --disable-option-checking >> '--prefix=/usr/local' '--build=i686-pc-mingw32' '--enable-jlink' >> '--enable-ft22 >> 32_libftdi' 'build_alias=i686-pc-mingw32' --cache-file=/dev/null >> --srcdir=../../ >> jimtcl >> ../../jimtcl/configure: line 3: >> D:/work/openocd/openocd-0.5.0/jimtcl/autosetup/j >> : No such file or directory >> ../../jimtcl/configure: line 3: exec: >> D:/work/openocd/openocd-0.5.0/jimtcl/autos >> : cannot execute: No such file or directory >> configure: error: ../../jimtcl/configure.gnu failed for jimtcl > > You have something weird going on there. Note how the lines are truncated. > For example: > >> ../../jimtcl/configure: line 3: >> D:/work/openocd/openocd-0.5.0/jimtcl/autosetup/j >> : No such file or directory
Yes I agree that the error message is quite strange. It is directly copy and paste from the Cygwin prompt. I will check again. The other errors under MinGW are also quite strange. I think I will try another setup. > Or is that your cut and paste of the error messages? > If so, please add the errors as an attachment instead. > > FYI: I build the release tarball on windows/mingw without any problems. Glad to know that. As per the previous answer from Spen that MinGW/Msys is not supported by jimtcl. Is that not true? -- Xiaofan _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development