Date: Wed, 24 May 2006 15:03:39 -0500
Message-Id: <200605242003.k4OK3dj01609@f7.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: karl AT freefriends DOT org (Karl Berry)
To: dave DOT korn AT artimi DOT com
Cc: cygwin AT cygwin DOT com, bug-automake AT gnu DOT org, bug-texinfo AT gnu DOT org
Subject: RE: Cygwin: texi2dvi stumbles over texinfo.tex (was: failed checks 	for automake 1.9.6)
In-Reply-To: <041d01c67e6e$a7fff670$a501a8c0@CAM.ARTIMI.COM>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

      Ok, you got me curious.  How does TeX know what application wrote the file
    if it's not "to do with" the contents of that file?

Sorry, I was referring to the one-line source file
\input texinfo @bye

As for the .fmt file, yes, it surely records whether tex, etex, pdfetex,
etc., was used to generate it.  Hence the error.

Ralf, what is the output if you run
  tex \\end
from the command line?  Also
  etex \\end
and
  pdfetex \\end

    This is e-TeXk, Version 3.141592-2.2 (Web2C 7.5.4)

This shows that texi2dvi is invoking etex.

    This is pdfeTeXk, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (INITEX)

This shows that mktexfmt is invoking pdfetex to build etex.fmt.

This mismatch is causing the error.

This is controlled by the file fmtutil.cnf.  What does that file look
like in your installation?

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/