On Thu, Aug 11, 2011 at 4:33 PM, Vit Mares <mares....@gmail.com> wrote: > what is the actual directeory when you run > ../configure > <DOT><DOT>/configure
mkdir build cd build ../configure --xxxxxxxxxx > 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=/home/maresv/openocd_dist_050' '--enable > -parport' '--enable-parport-giveio' '--enable-ft2232_ftd2xx' > '--with-ftd2xx-win32-zipdir=/home/maresv/drivers_ftdi' --ca > che-file=/dev/null --srcdir=. > 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 still a myth to me. I have one PC working (XP Pro SP3) and two other PCs not working (Vista 32bit Home and Win7 32bit Ultimate), all with updated MinGW.org MinGW distribution. I think Spen and Steve are working on the fix. https://lists.berlios.de/pipermail/openocd-development/2011-August/020537.html -- Xiaofan _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
