On 2012-1-30 3:21, Eli Zaretskii wrote:
>> Date: Sun, 29 Jan 2012 19:57:33 +0100 (CET)
>> From: Werner LEMBERG<wl@...>
>> Cc: bug-autoconf@...
>>> How did CRLF get there anyway? How did you extract or obtain the
>> `git clone' using msysgit, which uses CRLF by default for checkout
>> (provided the files are stored as LF within git, as it is for my
>> repository). I know how to circumvent the problem, but I was fooled
>> by the `msys' part in msysgit's name, thinking that those MSYS and
>> msysgit fit together without additional tweaks...
> You should set up msysgit to leave the EOLs alone. When you installed
> msysgit, it offered that as an option. In fact, I think this is the
> default, but maybe I'm wrong. In any case, letting a VCS change the
> EOL format is asking for trouble.
I have meet this issue for several times when building gdb under MSYS+MinGW, and this really wastes a lot of time until I finally debug to find that MSYSGIT just automatically change the EOL, and CRLF can't be handled by autotools/awk/sed system.
There is an option to force MSYSGIT not do such conversion.
> Git can handle this by auto-converting CRLF line endings into LF when you commit, and vice versa when it checks out code onto your filesystem. You can turn on this functionality with the core.autocrlf setting. If you’re on a Windows machine, set it to true — this converts LF endings into CRLF when you check out code:
> $ git config --global core.autocrlf true
So, you should set this option to "false" here. When you reinstall or upgrade your msysgit (I usually use portable Msysgit), don't forget to do this, otherwise you will meet this issue again.
ollydbg from codeblocks' forum