public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: TeX now vs. Tex in legacy version
Date: Fri, 20 Jul 2012 18:26:00 -0000	[thread overview]
Message-ID: <87a9yub87s.fsf@Rainer.invalid> (raw)
In-Reply-To: <5009352E.1080604@cornell.edu>

Ken Brown writes:
> On 7/20/2012 2:01 AM, Fergus wrote:
>> 1. Currently, having recently upgraded, I can't use latex:
>> $ latex a8.tex
>> This is pdfTeX, Version 3.1415926-2.4-1.40.13 (TeX Live 2012/Cygwin)
>>   restricted \write18 enabled.
>> ---! /var/lib/texmf/web2c/pdftex/latex.fmt doesn't match pdftex.pool
>> (Fatal format file error; I'm stymied)
>
> It looks like something went wrong with your installation of
> texlive-collection-latex.  See

This happened to me as well when first upgrading from teTeX to TeXlive.
The error message indicates that a different binary produced the format
file than the binary that is now trying to use it.  When this happens
after upgrading it seems to be related to a symlink not pointing to
where it should (in this case there seems to be a latex.exe file where
there should be a symlink from latex->pdftex.exe).  Since re-installing
the whole of TeXlive takes so much time I just re-linked everything and
ran the script that creates the format files.  I think the fact that
some of these links are created from texconfig may be the source of the
problem, maybe you could check if the installation really cleans all
symlinks (and unexpected executables where a symlink should be
installed) before creating the formats.  The executables generally
seem to come from the updated distribution, so I think it may just be an
interaction between some of the postinstall scripts.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada


--
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

  reply	other threads:[~2012-07-20 18:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-20  6:02 Fergus
2012-07-20 10:39 ` Ken Brown
2012-07-20 18:26   ` Achim Gratz [this message]
2012-07-20 19:08     ` Ken Brown
2012-07-20 20:01       ` marco atzeri
2012-07-20 20:06         ` Yaakov (Cygwin/X)
2012-07-20 20:17           ` marco atzeri
2012-07-20 20:28       ` Achim Gratz

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=87a9yub87s.fsf@Rainer.invalid \
    --to=stromeko@nexgo.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).