> Date: Fri, 20 Sep 2024 19:29:14 +0200 > From: Patrice Dumas <[email protected]> > > An issue with XS modules configure for mingw (on cygwin) using Bruno CI > https://github.com/gnu-texinfo/ci-check > > In tp/Texinfo/XS/configure.ac, we use perl -V:var to get information on > Perl configuration for the var. The perl output in that case has ^M > carriage returns at end of lines. This prevents the configure script to > work correctly. We parse perl -V:var output using a sed script. It > would be easy to add > s/\r// > to remove carriage returns. However, I fear that it could break some > native builds that expect carriage returns at end of lines. > > The symptom of this issue are line like that in tp/Texinfo/XS/configure > run output, while previous lines do not have a ^M: > checking Perl configuration value cc... gcc';^M > > 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. 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?
