public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: TexLive's ConTeXt runtime error..
Date: Wed, 22 Aug 2012 20:25:00 -0000	[thread overview]
Message-ID: <87mx1mlmck.fsf@Rainer.invalid> (raw)
In-Reply-To: <CAM-A7MBx8ZCdptx60yopFk-T_O-gjiVrHDX_xcamokyi3oup3w@mail.gmail.com>

Wynfield Henman writes:
> I reinstalled all cygwin zlib modules and the problem persisted.  The
> only zlib I found was the cygwin installed one.  Since it is POSIX
> compliant and TeXLive installs with it it shouldn't be a problem, I
> should think.  But, there is one due to, pdftex I think.

The file to look for is the zlib.h header file.

>>> This results in: "PANIC: unprotected error in call to Lua API
>>>                          (zlib library version does not match -
>>> header: 1.2.5, library: 1.2.7)"

The Lua component of ConTeX has been compiled with a 1.2.5 header file.
If you didn't have that version installed at the time you compiled
TeXlive, then there must be another zlib.h, probably delivered with
TeXlive.  You need to configure the build to use Cygwins zlib.h instead.


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

Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds


--
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-08-22 20:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-20 21:37 Wynfield Henman
2012-08-21  0:54 ` Ken Brown
2012-08-22 19:16   ` Wynfield Henman
2012-08-22 20:14     ` Ken Brown
2012-08-23 11:14       ` Wynfield Henman
2012-08-21 14:39 ` Achim Gratz
2012-08-22 19:30   ` Wynfield Henman
2012-08-22 20:25     ` Achim Gratz [this message]

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=87mx1mlmck.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).