From: Peter Korsgaard <peter@korsgaard.com>
To: "Raphaël Mélotte" <raphael.melotte@mind.be>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/mupdf: fix building with zlib-ng
Date: Fri, 09 Jun 2023 10:11:18 +0200 [thread overview]
Message-ID: <87fs7112e1.fsf@48ers.dk> (raw)
In-Reply-To: <20230425070923.1294644-1-raphael.melotte@mind.be> ("Raphaël Mélotte"'s message of "Tue, 25 Apr 2023 09:09:22 +0200")
>>>>> "Raphaël" == Raphaël Mélotte <raphael.melotte@mind.be> writes:
> The current mupdf version fails to build when zlib-ng is used as the
> zlib implementation. Add a patch to fix it.
> This fixes the following build failure raised since the bump to
> version 1.21.0 of the mupdf package in commit
> 3c2033cd2ace077e7dfaf58a2589b2a93a5fd7b0:
> source/fitz/encode-basic.c: In function 'deflate_write':
> source/fitz/encode-basic.c:343:27: error: 'UINT_MAX' undeclared (first use in this function)
> 343 | newbufsize = n >= UINT_MAX ? UINT_MAX : deflateBound(&state->z, n);
> | ^~~~~~~~
> source/fitz/encode-basic.c:26:1: note: 'UINT_MAX' is defined in header '<limits.h>'; did you forget to '#include <limits.h>'?
> Fixes: http://autobuild.buildroot.net/results/87128e9967cff20078c65ab847877aa44cc409d9
> Signed-off-by: Raphaël Mélotte <raphael.melotte@mind.be>
Committed to 2023.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-06-09 8:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 7:09 [Buildroot] [PATCH 1/1] package/mupdf: fix building with zlib-ng Raphaël Mélotte
2023-05-08 21:02 ` Yann E. MORIN
2023-05-09 11:58 ` [Buildroot] [PATCH v2 1/1] package: busybox: backport fix for missing getrandom() Raphaël Mélotte via buildroot
2023-05-09 18:50 ` Yann E. MORIN
2023-06-09 9:10 ` Peter Korsgaard
2023-06-09 8:11 ` Peter Korsgaard [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=87fs7112e1.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=raphael.melotte@mind.be \
/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