On 22/08/2023 17:55, ASSI via Cygwin wrote:
Ken Brown via Cygwin writes:
On 8/21/2023 11:02 AM, ASSI via Cygwin wrote:
(although in this case maybe i got spooked by the change
from 1.2.x to 1.3)
It looks like that's exactly what happened. The version check
compares the first 4 characters of
Ken Brown via Cygwin writes:
> On 8/21/2023 11:02 AM, ASSI via Cygwin wrote:
>> (although in this case maybe i got spooked by the change
>> from 1.2.x to 1.3)
>
> It looks like that's exactly what happened. The version check
> compares the first 4 characters of the version string.
Almost exactly
On 8/21/2023 11:02 AM, ASSI via Cygwin wrote:
(although in this case maybe i got spooked by the change
from 1.2.x to 1.3)
It looks like that's exactly what happened. The version check compares
the first 4 characters of the version string.
Ken
--
Problem reports: https://cygwin.com/pro
Ken Brown via Cygwin writes:
> Thanks for the report. I think I can fix this by rebuilding the TeX
> Live binaries with the new zlib. I'll do that ASAP.
The ABI hasn't changed, so it would be good if you relaxed or removed
this check. I've done that in a few other packages over the years. For
On 8/21/2023 3:31 AM, Per Larsson via Cygwin wrote:
After the latest update of zlib (1.2.13 -> 1.3), I’ve got a problem using
lualatex:
“lualatex failed: PANIC: unprotected error in call to Lua API (zlib library
version does not match - header: 1.2.13, library: 1.3)”
It can be avoided by res
After the latest update of zlib (1.2.13 -> 1.3), I’ve got a problem using
lualatex:
“lualatex failed: PANIC: unprotected error in call to Lua API (zlib library
version does not match - header: 1.2.13, library: 1.3)”
It can be avoided by resetting zlib to the previous version, but reporting her
6 matches
Mail list logo
