Re: Texinfo 7.2.90 build with mingw.org's MinGW: testing

> Date: Sun, 18 Jan 2026 16:49:38 +0100
> From: [email protected]
> Cc: [email protected], [email protected]
> 
> On Sat, Jan 17, 2026 at 12:40:07PM +0200, Eli Zaretskii wrote:
> > AFAICT, the only differences are:
> > 
> >   . I get diffs, whereas you don't
> >   . in my case the command says TEST=1, not TEST=2
> >   . the exit status is 1 and not 0
> > 
> > Does this give any clues as to what is going on?
> 
> Not really.  If TEST=2, there are additional checks of reference count
> of Perl objects, you probably do not have the modules needed by that.
> It is not important, the bugs that can be found like that are not
> important bugs and probably not platform dependent.  So TEST=1 is ok,
> and should not interfere with this test.
> 
> Maybe something that could be done easily to check the file name used
> for the Info file would be to call texi2any.pl with --verbose, so like:
> 
> /d/usr/Perl/bin/perl -w ./..//perl/texi2any.pl  --force --conf-dir ./../perl/t/init/ --conf-dir ./../perl/init --conf-dir ./../perl/ext -I ./formatting -I formatting/ -I ./ -I . -I built_input -I built_input/non_ascii --error-limit=1000 -c TEST=1 --verbose --output formatting/out_parser/reuse_macro_expand_file/ --macro-expand=formatting/out_parser/reuse_macro_expand_file/simplest.info ./formatting/simplest.texi
> 
> In my case, I get this information:
>   Output file formatting/out_parser/reuse_macro_expand_file/simplest.info
> 
> If it is not the same, it could explain why there is no 'overwriting
> file' warning.

I see this:

  Output file formatting\out_parser\reuse_macro_expand_file/simplest.info

So something, probably Perl I'm using (being a Windows port of Perl),
outputs file names with backslashes, and then some other code probably
compares file names as simple strings.  Could that be the reason?