Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com Subject: Re: tetex 3.0.0-3 format file problem [tetex maintainer -- please respond] References: <365B741739683A43A84B3AA09C16AA21579FEA AT EXCH01 DOT purdue DOT lcl> <20050519195924 DOT GE13760 AT trixie DOT casa DOT cgf DOT cx> From: Jan Nieuwenhuizen Date: Fri, 20 May 2005 09:09:22 +0200 In-Reply-To: <20050519195924.GE13760@trixie.casa.cgf.cx> (Christopher Faylor's message of "Thu, 19 May 2005 15:59:24 -0400") Message-ID: <87ekc2s7a5.fsf@peder.flower> User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes Christopher Faylor writes: > Jan, can you provide any insight here? What happened here is that the latex FMT file was somehow produced by plain tex, not by pdfetex. In tetex-2.x, latex was a symlink to tex, whereas in 3.0 it is a symlink to pdfetex. The FMT files are produced by running texconfig-sys init, which is run during postinstall. The latex-pdfetex version chokes on the invalid FMT file, so that file must be regenerated. The most common problems have to do with file permissions or manually edited config files. Easiest is to rerun setup.exe and reinstall the tetex-base package and see if that works. Otherwise, remove the latex.fmt file (`kpsewhich latex.fmt' prints the full file name). Run `texconfig-sys init' to generate the latex.fmt file. I'd be interested to learn what exactly did not work, or what fixed it. Jan. -- Jan Nieuwenhuizen | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org -- 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/