Re: texinfo-7.0.1 on OpenSolaris

[Gavin Smith]

On Sun, Jan 01, 2023 at 09:48:47PM +0100, Patrice Dumas wrote:
> This looks like a failure of formatting
> manual_include_accented_file_name_latin1 test, which could be checked
> separately with
> 
> ./run_parser_all.sh -dir formatting manual_include_accented_file_name_latin1
> 
> But it is a bit strange that the error seems to come from a shell, and
> not from perl.

No tests at all are run.  I thought that mksh was the shell that
make is using to run commands, but there is no "mksh" program on the
system and "mksh" appears to be hard-coded in error messages in the
make exectable (seen in the output of "strings /usr/bin/make".

I'm yet to work out how to get logs out of the virtual machine, other
than taking a screenshot, so in the interim here is a screenshot of
the output from "make check |& tee log" under tp/tests.  I made
sure that input_file_names_recoded_stamp.txt and the file with the
Latin-1 name were deleted first.

It is not clear if the command in the screenshot was involved at all
(e.g. with wildcard expansion).  The results are inconsistent and
this command is not always printed.

In fact, if I make a completely new Makefile, foo.Mak with the contents

foo:
        echo hello

and then run "make -f foo.Mak foo" the same error is printed.

> mksh: Fatal error: The string `included_la<A7>n1.texi' is not valid in 
> current locale

This version of make doesn't appear to tolerate non-locale-valid
filenames in the current directory at all.  (I also checked this in
a separate directory where the original Makefile wasn't present.)

One way of fixing this might be to put the generated file in a
subdirectory so that make can't see it.  Or it might not be worth
bothering as this version of make and/or operating system isn't
very important.  Another alternative is to remove the Latin-1 filename
tests completely for all systems.

openindiana-log.png
Description: PNG image