public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Fix gdb/doc/ PDF build on Fedora Rawhide==F-29
Date: Sun, 01 Apr 2018 04:46:00 -0000	[thread overview]
Message-ID: <20180401044646.GA21364@host1.jankratochvil.net> (raw)
In-Reply-To: <3b49baa5f0d1ca5676df3a9f78113abe@polymtl.ca>

On Sun, 01 Apr 2018 01:44:16 +0200, Simon Marchi wrote:
>   # 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?

Thanks, filed:
	Regression from F-28: texinfo PDF document no longer builds
	https://bugzilla.redhat.com/show_bug.cgi?id=1562580


> 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.

GDB sources carry even readline/, zlib/ and intl/ from which at least that
readline/ causes --with-system-readline to be buggy and despite causing such
problems they are still there.  My guess is it is so because some OS which
disappeared 30 years ago did miss them.


Jan

  reply	other threads:[~2018-04-01  4:46 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
2018-04-01  4:46   ` Jan Kratochvil [this message]
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=20180401044646.GA21364@host1.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    /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).