Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Subject: [patch] Fix gdb/doc/ PDF build on Fedora Rawhide==F-29
Date: Sat, 31 Mar 2018 17:32:00 -0000	[thread overview]
Message-ID: <20180331173219.GA18607@host1.jankratochvil.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 587 bytes --]

Hi,

on Fedora Rawhide==F-29 PDF build fails with:
	https://kojipkgs.fedoraproject.org//work/tasks/2102/26052102/build.log
	texi2dvi --pdf  -I ../../../gdb/doc/../mi -I ../../../gdb/doc \
		../../../gdb/doc/gdb.texinfo
	! I can't find file `texinfo.tex'.

TBH I do not see how the file could be found in earlier versions.  Also both
F-29 and F-28 have texinfo-tex-6.5-3.fc28.x86_64 while in F-28 it still builds
fine but in F-29 it does not - so apparently it depends on some other package.

But I did not investigate why as IMO the patch below is a logical one.

OK for check-in?


Jan

[-- Attachment #2: gdb-texinfo-path.patch --]
[-- Type: text/plain, Size: 489 bytes --]

gdb/ChangeLog
2018-03-31  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* doc/Makefile.in (TEXI2DVI): Add $(SET_TEXINPUTS).

diff --git a/gdb/doc/Makefile.in b/gdb/doc/Makefile.in
index 0323bc4ecb..fa745b3542 100644
--- a/gdb/doc/Makefile.in
+++ b/gdb/doc/Makefile.in
@@ -63,7 +63,7 @@ MAKEHTMLFLAGS =
 TEXI2ROFF=texi2roff
 
 # where to find texi2dvi, ditto
-TEXI2DVI=texi2dvi
+TEXI2DVI=$(SET_TEXINPUTS) texi2dvi
 
 # Package to install the docs under
 PACKAGE = @PACKAGE@
-- 
2.17.0.rc1


             reply	other threads:[~2018-03-31 17:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-31 17:32 Jan Kratochvil [this message]
2018-03-31 23:44 ` Simon Marchi
2018-04-01  4:46   ` Jan Kratochvil
2018-04-02 16:58     ` cancel: " Jan Kratochvil

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=20180331173219.GA18607@host1.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@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