Thank you very much but no success.
It is on Windows XP Pro SP3 and fresh MinGW instalation.
Best regards
Vit
2011/8/11 Xiaofan Chen :
> On Thu, Aug 11, 2011 at 4:33 PM, Vit Mares wrote:
> It is still a myth to me. I have one PC working (XP Pro SP3) and
> two other PCs not worki
Dear Xiaofan,
what is the actual directeory when you run
../configure
/configure
How did you manage the jimtcl problem on MinGW, I still end with
=== configuring in jimtcl (/home/maresv/openocd-0.5.0/jimtcl)
configure: running /bin/sh ./configure.gnu --disable-option-checking
'--prefix
is not so important the drivers are.
Best regards
Vit Mares
2011/8/10 Xiaofan Chen :
> BTW, based on my tests a whole ago, FTD2xx does not actually
> offer any significant speed advantages compare to libftdi/libusb-win32
> for openocd under Windows. So you may want to try out libf
The problem with jimsh, jimsh0 on MinGW build is probably somewhere in
the script chain
jimtcl/configure
jimtcl/autosetup/find-tclsh
jimtcl/autosetup/test-tclsh
BTW it will not accept jimsh version lesser than 0.70 as can be seen
in test-tclsh script.
Best regards
Vit
_
I also vote for Freddie, he is the sureness where everybody finds
usable binary release for Windows.
It is very important for embedded developers (not only for beginners)
to have the possibility of using running version instead of the only
you-can-build-it-though-but-first-install-Cygwin-then-find-
Hi Spen,
it doesn't seem so, jimsh0.exe is built during configure and is runable.
When I start it in MSYS console I get the dot prompt.
Best regards
Vit
2011/8/9 Spencer Oliver :
> On 9 August 2011 12:52, Vit Mares wrote:
>> Attempt to build 0.5.0 with MinGW on Windows
ine 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
Best
