On Wed, Aug 10, 2011 at 6:35 PM, Spencer Oliver <s...@spen-soft.co.uk> wrote:
> On 10 August 2011 11:15, Steve Bennett <ste...@workware.net.au> wrote:
>>> for me jimtcl has never built under msys since the update.
>>> log is attached below, for info jimsh0.exe is built ok.
>>>
>>> No installed jimsh or tclsh, building local bootstrap jimsh0
>>> The system cannot find the path specified.
>>> autosetup/system.tcl:150: Error:
>>> in procedure 'use' called at file "auto.def", line 5
>>> in procedure 'use' called at file "autosetup/cc.tcl", line 29
>>> in procedure 'config_guess' called at file "autosetup/system.tcl", line 150
>>> Try: 'configure --debug' for a full stack trace
>>> configure: error: ./configure.gnu failed for jimtcl
>>
>> It is failing while trying to run config.guess.
>>
>> What do you get when you run:
>>
>> sh jimtcl/autosetup/config.guess
>>
>
> i686-pc-mingw32
> just installed a fresh copy of msys/mingw - still same error.

I can reproduce here at a Vista 32bit installation of MinGW/MSys. It is
a myth now that I have the other PC working (XP SP3). I have updated
both MinGW/MSys installation to the latest.

=== configuring in jimtcl (/d/work/openocd/openocd-0.5.0/build_mingw/jimtcl)
configure: running /bin/sh ../../jimtcl/configure.gnu --disable-option-checking
'--prefix=/usr/local'  '--enable-jlink' '--enable-ft2232_libftdi' --cache-file=/
dev/null --srcdir=../../jimtcl
No installed jimsh or tclsh, building local bootstrap jimsh0
The system cannot find the path specified.
../../jimtcl/autosetup/system.tcl:150: Error:
in procedure 'use' called at file "../../jimtcl/auto.def", line 5
in procedure 'use' called at file "../../jimtcl/autosetup/cc.tcl", line 29
in procedure 'config_guess' called at file "../../jimtcl/autosetup/system.tcl",
line 150
Try: 'configure --debug' for a full stack trace
configure: error: ../../jimtcl/configure.gnu failed for jimtcl


-- 
Xiaofan
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to