[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: texinfo-5.9.90 pretest available

From: Gavin Smith
Subject: Re: texinfo-5.9.90 pretest available
Date: Tue, 24 Feb 2015 17:59:53 +0000

On 24 February 2015 at 16:39, Eli Zaretskii <address@hidden> wrote:
> Next, "make check" fails because info/pseudotty.c cannot be possibly
> compiled on Windows (and I'm not sure how portable it is to Posix
> platforms, either).  This is bad news for the MinGW port, because most
> of the Info brand-new test suite will not run.  I found and ran all
> the non-interactive tests by hand, but it would be nice if (1) there
> were a way to at least run those non-interactive tests automatically
> where pseudotty cannot be used; and (2) how about including in the
> scripts that implement interactive tests instructions for running them
> manually?  I think being able to run the tests on any supported
> platform is important.

Because pseudotty is in check_PROGRAMS in info/Makefile.am, "make
check" will first try to build pseudotty. There may be a way round it
with configure checks and Automake conditionals. Although I don't feel
it's very important to get the test suite to work under difficult

> This is because texi2any.pl uses "#! /usr/bin/env perl", which the
> version of Bash I use doesn't grok.  Is this really needed? other
> scripts that are installed by "make install" use just "/bin/perl".

This is to find the location of the perl executable in the search
path. For example, on my system the file "/bin/perl" doesn't exist.
Does "/usr/bin/env" exist for you? (As far as I know the reading of
the "#!" line is not done by the shell itself, but by the kernel -
could be wrong though.)

> Finally, dir-file-sloppily.sh fails:
>      info: No menu item 'File-M' in node '(dir)Top'.
> Does this test work on other systems?  It looks like the command line
> of the test is incorrect, because running the test with --debug=-1
> shows this:
>      $ ./t/dir-file-sloppily.sh && echo OK
>      info: adding ./t/infodir to INFOPATH
>      info: looking for file "FiLe-M"
>      info: looking for file FiLe-M in ./t/infodir
>      info: falling back to manpage node
>      info: No menu item 'FiLe-M' in node '(dir)Top'.
>      info: writing node (*manpages*)FiLe-M...
>      info: closing -
> IOW, it interprets "FiLe-M" as a file name, and then falls back to man
> pages.  To solve this, I needed to change the command line to this:
>      $GINFO --output - -f ${srcdir}/t/infodir/dir FiLe-M | grep "^File: 
> file-menu,"

That would be a different test. It should be looking for a menu entry
in the dir file, which I suspect is not being found. I suspect this is
because the infokey file is not being read. For me, I get the
following output:
info: "./t/Infokey-config", line 2: unknown action `xxx-not-recognized'
info: "./t/Infokey-config", line 3: cannot bind key sequence to menu-digit
File: file-menu,   Node: Top

As you see, there are messages there about reading the init file.

I've noticed there is no error message if you use "--init-file" for a
non-existent file, so that should be fixed.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]