I think it would be very nice if patch.exe could be made to handle different line endings in a transparent way. After all patch.exe is in those cases used to handle lines and any human can see what has to be done. Why should not patch.exe do the right thing then?
I would suppose that would mean that the output file should have the same line ending style as the file beeing patched. Apart from that line endings should not matter IMO. Eric Promislow wrote: > Thanks. This is part of a very large build system, so it made > more sense for me to change the line-endings of the patch > files and set their svn:eol-style to "native" than to change > the build process. > > - Eric > > Kees Zeelenberg wrote: >> ----- Original Message ----- >> From: "Eric Promislow" <[EMAIL PROTECTED]> >>> The patch files had Unix line-ends, not Windows line-ends, >>> so the non-cygwin patch.exe wasn't accepthing them. Unfortunately >>> it wasn't detecting that situation, just crashing. >> This seems related to the "Assertion failed, hunk, file patch.c, line >> 343"-problem mentioned on >> http://gnuwin32.sourceforge.net/packages/patch.htm >> The patchfile must have MS-Windows line endings (CRLF) or you must use >> the --binary option (and then the patched files will also have LF line >> endings). >> >> Kees Zeelenberg ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ GnuWin32-Users mailing list GnuWin32-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gnuwin32-users
