From: Joseph Myers <joseph@codesourcery.com>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: Doug Evans <xdje42@gmail.com>, Phil Muldoon <pmuldoon@redhat.com>,
<gdb@sourceware.org>
Subject: Re: Documentation build regressions
Date: Thu, 31 May 2018 17:23:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1805311721310.2935@digraph.polyomino.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.00.1805301840590.10896@tp.orcam.me.uk>
On Wed, 30 May 2018, Maciej W. Rozycki wrote:
> The latter file and offending line has been modified since and still fails
> in a similar manner. If I revert both files to just before the respective
> commits, then `make pdf' succeeds. This is with:
>
> This is pdfeTeXk, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
What texinfo.tex gets used? Is it the one from the binutils-gdb source
tree (which is over nine years old) or one from your TeX installation (and
if the latter, which version is it)?
I suppose it's possible that sometimes one gets used and sometimes the
other and your issue is specific to a particular texinfo.tex version.
Another possibly relevant version is that of texi2dvi.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-05-31 17:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 17:59 Maciej W. Rozycki
2018-05-30 20:12 ` Tom Tromey
2018-05-30 20:56 ` Jan Kratochvil
2018-05-31 17:23 ` Joseph Myers [this message]
2018-06-01 14:01 ` Jan Kratochvil
2018-06-01 19:38 ` Joseph Myers
2018-06-04 20:27 ` Maciej W. Rozycki
2018-06-05 9:49 ` variable displayed twice when using GDB/MI Xavier Roirand
2018-06-07 11:33 ` Pedro Alves
2018-05-31 17:51 ` Documentation build regressions Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1805311721310.2935@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=macro@mips.com \
--cc=pmuldoon@redhat.com \
--cc=xdje42@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox