On Tue, Jun 9, 2009 at 1:02 PM, Zach Welch<z...@superlucidity.net> wrote:
> On Tue, 2009-06-09 at 12:54 +0200, Øyvind Harboe wrote:
>> > Some more information about the subject:
>> >
>> >  http://www.cygwin.com/ml/cygwin/2008-12/msg00525.html
>> >
>> > I particularly like the postscript. :)  We are not alone here.
>>
>> I'm just going to close my eyes and hope I never hear of this
>> again :-)
>
> Not so fast.
>
> Can we reset the configure.in and Makefile.am svn:eol-style properties?
> If these changes did not fix a problem, then I would like to see these
> reverted to prevent future line-ending issues in these files.

Done. It was a red herring and I've set it back.

>> I've grepped the source tree and "guess-rev.sh" was the .sh
>> file that is used during normal builds that was broken.
>
> I am not sure what that means though.

If you try to run a .sh file under Cygwin and that file has Windows
line endings, it will fail w/a syntax error.

>> Don't know about this one though:
>>
>> ./tools/uncrustify1.sh
>
> Whose file is that?

Dunno.



-- 
Øyvind Harboe
Embedded software and hardware consulting services
http://consulting.zylin.com
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to