On 17/11/2010, at 2:32 PM, Andrew Leech wrote: > On Wed, Nov 17, 2010 at 8:05 AM, Steve Bennett <ste...@workware.net.au> wrote: >> On 16/11/2010, at 11:36 AM, Andrew Leech wrote: >> >>> On Tue, Nov 16, 2010 at 12:19 PM, Steve Bennett <ste...@workware.net.au> >>> wrote: >>>> >>>> On 16/11/2010, at 11:15 AM, Øyvind Harboe wrote: >>>> >>>>> On Tue, Nov 16, 2010 at 2:06 AM, Steve Bennett <ste...@workware.net.au> >>>>> wrote: >>>>>> On 16/11/2010, at 9:27 AM, Andrew Leech wrote: >>>>>> >>>>>>> Hi all, >>>>>>> I've just found a compiling/usage difficulty with the git version on >>>>>>> cygwin. Apparently somewhere between 0.4.0 and mainline (possibly >>>>>>> jimtcl?) openocd no longer handles dos line endings on config files. >>>>>>> Apparently all my config files of my existing 0.4.0 installation have >>>>>>> dos line endings and I'd never realised or cared, but I compiled git >>>>>>> on cygwin and tried to use it with my existing openocd.cfg and was >>>>>>> treated to this error: >>>>>>> > > <snip> > >> >> Perhaps you could try the attached patch to Jim Tcl. It should >> allow for cfg files with dos line endings. >> >> > < 0001--source-now-opens-the-script-file-in-text-mode.patch > > > This patch works for me, openocd.exe now works with new config files > (unix line endings) and my old ones (dos line endings).
Great. I've applied this in the latest version of Jim Tcl. Cheers, Steve -- µWeb: Embedded Web Framework - http://uweb.workware.net.au/ WorkWare Systems Pty Ltd W: www.workware.net.au P: 0434 921 300 E: ste...@workware.net.au F: 07 3102 9221 _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
