Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Fix gdb/doc/ PDF build on Fedora Rawhide==F-29
Date: Sat, 31 Mar 2018 23:44:00 -0000	[thread overview]
Message-ID: <3b49baa5f0d1ca5676df3a9f78113abe@polymtl.ca> (raw)
In-Reply-To: <20180331173219.GA18607@host1.jankratochvil.net>

On 2018-03-31 13:32, Jan Kratochvil wrote:
> 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

Hi Jan,

 From the logs of building it on F27, it is picked up at

   /usr/share/texlive/texmf-local/texmf-compat/tex/texinfo/texinfo.tex

   $ readlink -f 
/usr/share/texlive/texmf-local/texmf-compat/tex/texinfo/texinfo.tex
   /usr/share/texmf/tex/texinfo/texinfo.tex

which is probably in the default latex include dirs, I guess because of 
this line in texmf.cnf:

   TEXMFLOCAL = $TEXMFROOT/texmf-local//

The directory /usr/share/texlive/texmf-local exists on F27 and F28 but 
not on F29.  So the F29 config references a directory that does not 
exist.  Re-creating it and updating the tex hash:

   # mkdir /usr/share/texlive/texmf-local
   # ln -s ../../texmf /usr/share/texlive/texmf-local/texmf-compat
   # texhash

makes it work for me on F29.  So maybe there's actually a bug in the F29 
version of the texinfo package that you should report?  I have no idea 
if that change in the packaging was intended or not, but having the 
texinfo.tex file excluded from the default latex search path will 
probably break anything trying to use texinfo.

As for the version of texinfo.tex in the source tree, my guess is 
(correct me if I'm wrong) that it was put there in a time where it was 
not so readily available as a package in distros.  But realistically, 
today, everyone picks it up from their distro's texinfo package (which 
is proven by the fact that you didn't need to set TEXINPUTS to find the 
in-tree version until a distro package broke).

If we can now expect people to pick up texinfo.tex from their distro, 
then I think we should instead remove SET_TEXINPUTS altogether.

Simon


  reply	other threads:[~2018-03-31 23:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-31 17:32 Jan Kratochvil
2018-03-31 23:44 ` Simon Marchi [this message]
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=3b49baa5f0d1ca5676df3a9f78113abe@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.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