Build process chash when btyacc parse file was created in windows with end of line mark as \r\n

[Khalyutin]

if parsing file was created in windows but processing on linux we need  delete windows end of line mark as \r\n (CR + LF) Otherwise, the file will not be found.

more info: https://github.com/ChrisDodd/btyacc/pull/32

[aafemt]

Such problems are usually solved by .gitattributes file.

[Khalyutin]

Such problems are usually solved by .gitattributes file.

Yes, of course. But we tried to eliminate the root cause of the problem so that others wouldn't have to waste resources trying to localize it in the future. :)

[aafemt]

Will you also fix cmd.exe that cannot process files with LF-only EoLNs?

[Khalyutin]

Will you also fix cmd.exe that cannot process files with LF-only EoLNs?

source code of ms command interpreter not include in FirebirdSQL/firebird/extern/

[hvlad]

Why not pickup commit from original source tree ?

[Khalyutin]

Why not pickup commit from original source tree ?

the source tree is very different from the version of btyacc in extern/btyacc/ start from "read_from_file()" in original insted of "fopen()" in extern/btyacc/

Adding read_from_file() may require further changes, up to replacing the entire library :(.

As a result, fixing a known compilation error can addition unknown parsing errors...

I think the risk of taking a significant block of code from the btyacc original source is unjustified.