From: Ruud van der Pas <ruud.vanderpas@oracle.com>
To: binutils@sourceware.org
Subject: gprofng: update file texinfo.tex?
Date: Fri, 4 Feb 2022 13:32:02 +0100 [thread overview]
Message-ID: <F9C157CE-A4A6-4631-9239-D90884F95159@oracle.com> (raw)
Hi team,
I ran into an issue when trying to generate a PDF file from the gprofng.texi
Texinfo file.
I’m using Texinfo 6.7, but texi2pdf did not like my use of @subentry, while this
is supported in 6.7.
It took me quite some time to find out that this was caused by the texinfo.tex
file that is currently in subdirectory binutils-gdb/texinfo.
I was using this file to be more self contained, but it is from 2009 (2009-03-28.05).
Switching to the 2021 version (2021-02-20.11) solved the problem.
We could include the 2021 file in the gprofng/doc directory and use it instead, but
I wonder if it might be better to consider updating the current file in binutils-gdb/texinfo
to a more recent version.
Kind regards, Ruud
next reply other threads:[~2022-02-04 12:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 12:32 Ruud van der Pas [this message]
2022-02-10 11:19 ` Nick Clifton
2022-02-10 16:22 ` Ruud van der Pas
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=F9C157CE-A4A6-4631-9239-D90884F95159@oracle.com \
--to=ruud.vanderpas@oracle.com \
--cc=binutils@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).