zsh-workers
 help / color / mirror / code / Atom feed
From: "Jun T." <takimoto-j@kba.biglobe.ne.jp>
To: zsh-workers@zsh.org
Subject: Re: Conflict with Jun T's texi2any patch
Date: Sun, 24 May 2015 01:47:24 +0900	[thread overview]
Message-ID: <B209D689-3B48-4135-97F6-3F522ED68E7E@kba.biglobe.ne.jp> (raw)
In-Reply-To: <150522100546.ZM25066@torch.brasslantern.com>


2015/05/23 02:05, Bart Schaefer <schaefer@brasslantern.com> wrote:

> +AC_CHECK_PROGS([TEXI2PDF], [texi2pdf], [makeinfo --pdf])

> I presume texi2any can replace texi2pdf as well, if that's not found?

With texinfo-4.13, makeinfo does not support the option --pdf.

With texinfo-5.2, makeinfo (= texi2any) supports --pdf, but if I try

$ texi2any --pdf zsh.texi

then it fails as

zsh.texi:70: @menu seen before first @node

This is strange, because, as Peter wrote, texi2any can't produce pdf
by itself but calls 'texi2dvi --pdf'. Or at least the documentation
of texi2any says so.
('texi2pdf zsh.texi' or 'texi2dvi --pdf zsh.texi' works, of course).

Anyway I think if there is texi2any then there should be texi2dvi and
texi2pdf, unless a user (or a package manager) installed texinfo in a
very strange way.

texi2pdf (texinfo 4 or 5) is just a wrapper script for 'texi2dvi --pdf'.
If $(TEXI2PDF) is empty, then Doc/Makefile.in calls 'texi2dvi --pdf'
instead. So I think if texi2pdf is not found then leaving $(TEXI2PDF)
empty is OK (if texi2dvi does not exist then 'texi2any --pdf' will fail
even if the above problem has been fixed).

Or is it better to check the existence of texi2dvi in configure?


      parent reply	other threads:[~2015-05-23 16:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-22 17:05 Bart Schaefer
2015-05-22 21:27 ` Peter Stephenson
2015-05-23 10:13 ` Daniel Shahaf
2015-05-23 16:47 ` Jun T. [this message]

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=B209D689-3B48-4135-97F6-3F522ED68E7E@kba.biglobe.ne.jp \
    --to=takimoto-j@kba.biglobe.ne.jp \
    --cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).