From: "Maciej W. Rozycki" <macro@mips.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
Doug Evans <xdje42@gmail.com>, Phil Muldoon <pmuldoon@redhat.com>,
<gdb@sourceware.org>
Subject: Re: Documentation build regressions
Date: Mon, 04 Jun 2018 20:27:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1806042040490.6942@tp.orcam.me.uk> (raw)
In-Reply-To: <alpine.DEB.2.20.1806011936350.25633@digraph.polyomino.org.uk>
On Fri, 1 Jun 2018, Joseph Myers wrote:
> > > 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)?
> >
> > It is true it did not work when GDB doc build picked the shipped texinfo.tex.
>
> Thanks. In that case I advise that Maciej tries updating the shipped
> texinfo.tex to the current version -
> svn://svn.savannah.gnu.org/texinfo/trunk/doc/texinfo.tex - to see if that
> helps with the observed problem.
Thanks for the suggestion.
I have tried that, however that didn't change anything. I am able to
build `gdb.pdf' on another system though, which has:
This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015/Debian) (preloaded format=pdfetex 2018.5.30) 4 JUN 2018 20:59
so it looks to me like either triggering a bug in the old version or using
a feature present in the new version only. I have no strong opinion on
whether we should require a recent enough version of TeX or if we ought to
work with any version we might encounter.
FWIW I have always considered TeX a pretty conservative tool and I'm
quite surprised to see it fail in a version-dependent manner.
Maciej
next prev parent reply other threads:[~2018-06-04 20:27 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
2018-06-01 14:01 ` Jan Kratochvil
2018-06-01 19:38 ` Joseph Myers
2018-06-04 20:27 ` Maciej W. Rozycki [this message]
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.00.1806042040490.6942@tp.orcam.me.uk \
--to=macro@mips.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=joseph@codesourcery.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