On 14/07/2011, at 5:39 AM, Eric Wetzel wrote: > On Thu, Jul 7, 2011 at 8:07 AM, Eric Wetzel <thewet...@gmail.com> wrote: >> On Thu, Jul 7, 2011 at 6:40 AM, Spencer Oliver <s...@spen-soft.co.uk> wrote: >>> On 7 July 2011 11:09, Steve Bennett <ste...@workware.net.au> wrote: >>>> >>>> ../../jimtcl/autosetup/find-tclsh: line 10: cc: command not found >>>> >>>> But no cc? >>>> >>>> If cygwin is installed, why no cc? >>> >>> That one confused me aswell, perhaps the cygwin tools need reinstalling. >>> >>> The cygwin-mingw cross compiler is relatively new and does have some >>> install issues: >>> http://www.cygwin.com/ml/cygwin-announce/2011-06/msg00004.html >>> >>> Cheers >>> Spen >> >> That would do it. I didn't have Cygwin's gcc installed, only the mingw one. >> >> It built fine last week, with git ff640f1, but I guess the latest bump >> of JimTCL changed the way it builds. >> >> Thanks, >> ~Eric >> > > I have a new, but similar, issue with Jim now. After the last build > succeeded, I added OpenOCD's install directory to my Cygwin path, > which includes a mingw32-targetted Jim binary. Now, attempting to > rebuild OpenOCD from git results in this during the configure phase: > === configuring in jimtcl > (/home/ericwetz/local/src/openocd.git/build-win32/jimtcl) > configure: running /bin/sh ../../jimtcl/configure.gnu > --disable-option-checking '--prefix=/home/ericwetz/local' > '--enable-maintainer-mode' '--build=i686-pc-cygwin' > '--host=i686-pc-mingw32' '--enable-dummy' '--enable-jlink' > '--enable-ft2232_ftd2xx' > '--with-ftd2xx-win32-zipdir=/home/ericwetz/local/src/ftd2xx' > 'build_alias=i686-pc-cygwin' 'host_alias=i686-pc-mingw32' > --cache-file=/dev/null --srcdir=../../jimtcl > cygwin warning: > MS-DOS style path detected: > /home/ericwetz/local/bin/C:\cygwin\home\ericwetz\local\src\openocd.git\build-win32\jimtcl\x0D > Preferred POSIX equivalent is: > /home/ericwetz/local/bin/C:/cygwin/home/ericwetz/local/src/openocd.git/build-win32/jimtcl\x0D > CYGWIN environment variable option "nodosfilewarning" turns off this warning. > Consult the user's guide for more details about POSIX paths: > http://cygwin.com/cygwin-ug-net/using.html#using-pathnames > ../../jimtcl/configure: line 3: exec: > C:\cygwin\home\ericwetz\local\src\openocd.: not foundin32\jimtcl > configure: error: ../../jimtcl/configure.gnu failed for jimtcl > > Running the installed jimsh on jimtcl/autosetup/test-tclsh returns the > Windows path: > C:\cygwin\home\ericwetz\local\src\openocd.git\jimtcl > > It should be noted that running jimsh on an absolute Cygwin path > fails, complaining "No such file or directory", but that seems to be > typical of all native Windows applications. > > Removing jimsh from my path fixes this, as a new jimsh0 must be > bootstrapped (solved in this last post in this e-mail). > > I don't know what could be done to fix this; I'm not even sure it > deserves fixing. I acknowledge that the environments I'm trying to > build from and for are a little bit convoluted, but this is what I > have to work with. I don't have a Linux machine at work, and MinGW > always makes me kindof uncomfortable.
Hi Eric, Thanks for the report. This is caused by a couple of things. Firstly, the version of jimtcl used by openocd isn't fully functional when built under mingw. It's fine for openocd, but things like backslashes in paths and exec aren't handled properly. So the built jimsh isn't suitable for configure/autosetup. (Not that the latest version of jimtcl adds better support for mingw, but that version is not yet used by openocd) But, that wouldn't be a problem except for... Secondly, when openocd installs it also installs jimtcl. It really shouldn't. It uses jimtcl internally and doesn't need anything installed. At some point openocd will use a newer version of jimtcl, so this will solve the first point. But I would also like to see openocd *not* install jimtcl. This needs to be done with some automake-foo in openocd. Cheers, Steve -- µWeb: Embedded Web Framework - http://uweb.workware.net.au/ WorkWare Systems Pty Ltd W: www.workware.net.au P: +61 434 921 300 E: ste...@workware.net.au F: +61 7 3391 6002 _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
