Re: safe to remove carriage returns in configure for mingw?

[Patrice Dumas]

On Fri, Sep 20, 2024 at 08:54:09PM +0300, Eli Zaretskii wrote:
> > Date: Fri, 20 Sep 2024 19:29:14 +0200
> > From: Patrice Dumas <pertusus@free.fr>
> > 
> > Is this issue also happening with native builds?  Would it be safe to
> > always remove carriage returns?
> 
> What do you mean by "native builds"?  A MinGW build is a native
> Windows build, so I'm confused about the above dichotomy.

What the CI uses is mingw in Cygwin build.  If I understood well, this
is what is called a "fake" Cygwin to MinGW cross compile case in
https://www.gnu.org/software/libtool/manual/html_node/Cygwin-to-MinGW-Cross.html

So it is, in a way less native that mingw on MSYS, although it is also
native in a way...

> FWIW, I don't see any such problems in Texinfo 7.0.94: there are no ^M
> characters in tp/Texinfo/XS/config.log.  I don't know why.  Maybe
> `...` removes the ^M characters in my version of Bash?  Hmm...
> 
> Yes, looks that way:
> 
>   $ /d/usr/Perl/bin/perl -V:cc > foo
> 
> produces 'foo' with CRLF end-of-line, but
> 
>   $ echo `/d/usr/Perl/bin/perl -V:cc` > foo
> 
> produces 'foo' with Unix newlines.
> 
> Doesn't this happen with the Bash you are using?

That could be the difference.  The shell is
C:\cygwin\bin\bash.exe -eo pipefail -o igncr '{0}'

I would have thought that -o igncr would have meant that CR are removed,
though.

In any case, if the CR is removed for you too, removing it explicitely
with sed should make things right, so this is something I can do anyway,
thanks.  I will add a comment explaining in which case it seems to be
useful.

-- 
Pat