From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21485 invoked by alias); 23 May 2015 16:47:35 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 35278 Received: (qmail 17266 invoked from network); 23 May 2015 16:47:30 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.0 X-Biglobe-Sender: Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: Conflict with Jun T's texi2any patch From: "Jun T." In-Reply-To: <150522100546.ZM25066@torch.brasslantern.com> Date: Sun, 24 May 2015 01:47:24 +0900 Content-Transfer-Encoding: 7bit Message-Id: References: <150522100546.ZM25066@torch.brasslantern.com> To: zsh-workers@zsh.org X-Mailer: Apple Mail (2.1878.6) X-Biglobe-Spnum: 50760 2015/05/23 02:05, Bart Schaefer 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?