From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: yegorslists@googlemail.com
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/imlib2: add zlib dependency
Date: Sat, 12 Sep 2026 16:09:23 +0200 [thread overview]
Message-ID: <dbfbad3eaa00cc20757e6f26e249e181@free.fr> (raw)
In-Reply-To: <20260903095415.3657050-1-yegorslists@googlemail.com>
On 03/09/2026 11:54, yegorslists--- via buildroot wrote:
> From: Yegor Yefremov <yegorslists@googlemail.com>
>
> The demo programs, which have always been built and are still enabled
> by
> default, gained a zlib dependency in imlib2 1.12.3: upstream commit
> f8a451043871 ("imlib2_load: Add crc32 printout") started using zlib's
> crc32() in imlib2_load, and 31006b425e11 ("imlib2_view: Optionally show
> crc32 of image data") did the same for imlib2_view. Both hardcoded -lz.
>
> Upstream commit b9555030dace ("autofoo: don't hardcode zlib flags"),
> first released in 1.12.4, replaced -lz with $(ZLIB_LIBS) and added an
> unconditional PKG_CHECK_MODULES(ZLIB, zlib) to the demo programs branch
> of configure, turning the previously silent link-time requirement into
> a
> configure failure:
>
> checking for zlib... no
> configure: error: Package requirements (zlib) were not met:
>
> Package 'zlib' not found
>
> As Buildroot went straight from 1.7.3 to 1.12.5 the intermediate state
> was never packaged, but the dependency has in fact been missing since
> the
> crc32 support landed.
>
> Fixes:
> https://autobuild.buildroot.org/results/4e05404c353ef985d74757d0b1ec3eda2cdff523/
>
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-09-12 14:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 9:54 [Buildroot] [PATCH] package/imlib2: add zlib dependency yegorslists--- via buildroot
2026-09-12 14:09 ` Julien Olivain via buildroot [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=dbfbad3eaa00cc20757e6f26e249e181@free.fr \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=yegorslists@googlemail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.