> > Could there be something we could put in the "configure > script" - that > > tells CYGWIN - to behave? > > ie: Perhaps something like the SHELLOPTS thing? > > > > For example - maybe in the "bootstrap" script? > > And in the "CONFIGURE' script? > > And in the Makefiles? > > > > FYI - with SVN - is who thinks what is native and when. > > > > Tortiose - Native = Windows, period, no way to override this > > SVN - cygwin = Native = CYGWIN setting > > SVN - DOS = Native = Windows > > SVN - on a Linux box = Unix > > It's even more nasty, if you share something via SAMBA... > > Maybe I'm missing something subtle, but as I understand it, > the problem is that a shell script (which will never be > attempted to be run by native > Windows) is sometimes failing because it has CRLF "Windows" > line-endings. > > Why don't we set the svn:eol-style property on that file to > be LF? That way, it will always get LF and only LF line > endings, regardless of the system on which it is checked out. > > svn propset svn:eol-style 'LF' guess-rev.sh (and all other .sh files) >
Sorry i may have missed a lot of this thread (been away) but sh files should already have the 'LF' style. We had issues about a year ago and all the scripts were changed. Personally i should have never added the eol-style and forced all users to use 'LF' for everything - as openocd was originally. At that time some devs had issues with mixing line endings. For info this is how gcc svn works. Cheers Spen _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
