From: Rolf Dieterich <rolf.dieterich@gmx.de>
To: cygwin@cygwin.com
Subject: Re: Using texi2pdf
Date: Sun, 23 Oct 2011 07:10:00 -0000 [thread overview]
Message-ID: <j80eaf$lv$1@dough.gmane.org> (raw)
In-Reply-To: <201110212154120500.000CF89E@127.0.0.1>
Andreas Falkenhahn <andreas@falkenhahn.com> hat am 21.10.2011 um 21:54
Uhr geschrieben:
>
> Hi,
>
> I just tried to use texi2pdf on Cygwin but it doesn't seem to work right. There's a certain
> amount of program activity but no PDF is generated. Here's the verbose log:
>
> $ texi2pdf --verbose testfile.texi
> /usr/bin/texi2dvi: Processing testfile.texi ...
> /usr/bin/texi2dvi: BIBINPUTS='.:/home/Andreas:/home/Andreas/.::'
> /usr/bin/texi2dvi: BSTINPUTS='.:/home/Andreas:/home/Andreas/.::'
> /usr/bin/texi2dvi: DVIPSHEADERS='.:/home/Andreas:/home/Andreas/.::'
> /usr/bin/texi2dvi: INDEXSTYLE='.:/home/Andreas:/home/Andreas/.::'
> /usr/bin/texi2dvi: MFINPUTS='.:/home/Andreas:/home/Andreas/.::'
> /usr/bin/texi2dvi: MPINPUTS='.:/home/Andreas:/home/Andreas/.::'
> /usr/bin/texi2dvi: TEXINPUTS='.:/home/Andreas:/home/Andreas/.::'
> /usr/bin/texi2dvi: TFMFONTS='.:/home/Andreas:/home/Andreas/.::'
> /usr/bin/texi2dvi: Removing /home/Andreas/testfile.t2d
>
> Does anybody know why this doesn't work as it should?
>
> Tks,
>
> Andreas
Hi Andreas,
I happened to generate some texinfo manuals in pdf format lately. For me
it is working:
$ texi2pdf --verbose gccintro.texi
/usr/bin/texi2dvi: Processing gccintro.texi ...
/usr/bin/texi2dvi:
BIBINPUTS='.:/home/Rolf/info/gccintro-1.0:/home/Rolf/info/gccintro-1.0/.::'
/usr/bin/texi2dvi:
BSTINPUTS='.:/home/Rolf/info/gccintro-1.0:/home/Rolf/info/gccintro-1.0/.::'
/usr/bin/texi2dvi:
DVIPSHEADERS='.:/home/Rolf/info/gccintro-1.0:/home/Rolf/info/gccintro-1.0/.::'
/usr/bin/texi2dvi:
INDEXSTYLE='.:/home/Rolf/info/gccintro-1.0:/home/Rolf/info/gccintro-1.0/.::'
/usr/bin/texi2dvi:
MFINPUTS='.:/home/Rolf/info/gccintro-1.0:/home/Rolf/info/gccintro-1.0/.::'
/usr/bin/texi2dvi:
MPINPUTS='.:/home/Rolf/info/gccintro-1.0:/home/Rolf/info/gccintro-1.0/.::'
/usr/bin/texi2dvi:
TEXINPUTS='.:/home/Rolf/info/gccintro-1.0:/home/Rolf/info/gccintro-1.0/.::'
/usr/bin/texi2dvi:
TFMFONTS='.:/home/Rolf/info/gccintro-1.0:/home/Rolf/info/gccintro-1.0/.::'
/usr/bin/texi2dvi: texinfo.tex preloaded as `', version is `20110923' ...
/usr/bin/texi2dvi: Cycle 1 for ./gccintro.texi
/usr/bin/texi2dvi: Backing up xref files: gccintro.aux
gccintro.cp
gccintro.cps
gccintro.toc
/usr/bin/texi2dvi: Running texindex gccintro.cp
/usr/bin/texi2dvi: /usr/bin/texi2dvi: Running pdfetex --file-line-error
'./gccintro.texi' ...
This is pdfTeX, Version 3.1415926-2.3-1.40.12 (TeX Live 2011)
restricted \write18 enabled.
entering extended mode
[...]
But I have Tex Live 2011 installed. So I don't use tetex 3.0 from the
official Cygwin distribution:
$ kpsewhich texinfo.tex
/usr/local/texlive/2011/texmf-dist/tex/texinfo/texinfo.tex
First check if you have the texinfo format installed:
$ cygcheck -f /usr/share/texmf/tex/texinfo/texinfo.tex
tetex-base-3.0.0-3
texinfo-4.13-3
Then check if you have the tex engines installed, e.g. pdftex:
$ cygcheck -f /usr/bin/pdftex
tetex-bin-3.0.0-3
My tetex installation seems to be incomplete:
$ cygcheck -c tetex-bin
Cygwin Package Information
Package Version Status
tetex-bin 3.0.0-3 Incomplete
But as I mentioned I don't use tetex anyway.
Summary:
texi2pdf and texi2dvi are bash scripts which need texinfo.tex (a TeX
format) an underlying tex engine.
I don't know if the rather ancient tetex distribution in Cygwin is
sufficient to do the job.
-- Rolf
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2011-10-23 7:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 19:54 Andreas Falkenhahn
2011-10-23 7:10 ` Rolf Dieterich [this message]
2011-10-28 14:33 ` Andreas Falkenhahn
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='j80eaf$lv$1@dough.gmane.org' \
--to=rolf.dieterich@gmx.de \
--cc=cygwin@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).