bug-texinfo
[Top][All Lists]
Advanced

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

Re: Octave manual not buildable with texinfo from git master


From: Gavin Smith
Subject: Re: Octave manual not buildable with texinfo from git master
Date: Wed, 23 Sep 2020 17:08:30 +0100
User-agent: Mutt/1.9.4 (2018-02-28)

> 
> Hello,
> 
> I filed a report for octave.
> 
> https://savannah.gnu.org/bugs/index.php?59168
> 
> Best Regards
> 
> Stefan

I am getting closer to debugging it.  I deleted the file 
doc/interpreter/doc-cache and ran "make doc/interpreter/doc-cache".
This gave the errors but didn't show which command was being run by 
make other than printing

  GEN      doc/interpreter/doc-cache

After some time I found I could do

 make AM_V_GEN= doc/interpreter/doc-cache

which showed that it was running

perl ./doc/interpreter/mk-doc-cache.pl . ./doc/interpreter/macros.texi 
libinterp/DOCSTRINGS scripts/DOCSTRINGS > doc/interpreter/doc-cache-t && \
mv doc/interpreter/doc-cache-t doc/interpreter/doc-cache

Getting the script to print its makeinfo invocation showed it was 
running

makeinfo --no-headers --no-warn --force --no-validate --fill-column=1024 
/tmp/OyAtTnQAZi

Unfortunately the /tmp/OyAtTnQAZi file was deleted so I couldn't run 
this in isolation.  This is not straightforward to debug!  After copying 
the temporary file to another file (by sticking

  system "cp $texi_path /tmp/file";

in the script), I managed to get a file which was treated differently 
depending on whether TEXINFO_XS_PARSER was set to 0 (a file that was 
49,927 lines long).

I'm attaching this file to this email.

Now, when I remove the --force and --no-validate flags I get the same 
error messages with TEXINFO_XS_PARSER=0.  There is no XREFmovfun etc. 
node or anchor defined in the file itself, which makes me think that 
they are not supposed to defined.  The most likely explanation is that 
with TEXINFO_XS_PARSER=1 the errors are stopping the file from being 
processed and the --force flag is being ignored.  Does that sound right?

Attachment: test-file
Description: Text document


reply via email to

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