From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org,
Adrian Perez de Castro <aperez@igalia.com>,
Fabrice Fontaine <fontaine.fabrice@gmail.com>,
Joseph Kogut <joseph.kogut@gmail.com>,
Marcus Folkesson <marcus.folkesson@gmail.com>,
Romain Naour <romain.naour@gmail.com>,
Simon Dawson <spdawson@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/2] package/libepoxy: needs dynamic library
Date: Wed, 21 Oct 2026 23:17:37 +0200 [thread overview]
Message-ID: <atkr5cxe9AL1VtN3@windsurf> (raw)
In-Reply-To: <20260719125334.1772882-1-bernd@kuhls.net>
On Sun, Jul 19, 2026 at 02:53:33PM +0200, Bernd Kuhls wrote:
> Buildroot commit cd2583ca0a993cb44e8822966f101e820ac2619e removed the
> dependencies to gl/egl which revealed that libepoxy needs a toolchain
> with dynamic library:
>
> ../src/dispatch_common.c:166:10: fatal error: dlfcn.h:
> No such file or directory
> 166 | #include <dlfcn.h>
>
> This patch disables static builds and propagates reverse dependencies.
>
> Fixes:
> https://autobuild.buildroot.net/results/9d5/9d56cb52eb57df61184e26cea9604f1521d135f4/
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
Both applied to master, thanks!
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-10-21 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-19 12:53 [Buildroot] [PATCH 1/2] package/libepoxy: needs dynamic library Bernd Kuhls
2026-07-19 12:53 ` [Buildroot] [PATCH 2/2] package/libepoxy: needs threads Bernd Kuhls
2026-10-21 21:17 ` Thomas Petazzoni 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=atkr5cxe9AL1VtN3@windsurf \
--to=buildroot@buildroot.org \
--cc=aperez@igalia.com \
--cc=bernd@kuhls.net \
--cc=fontaine.fabrice@gmail.com \
--cc=joseph.kogut@gmail.com \
--cc=marcus.folkesson@gmail.com \
--cc=romain.naour@gmail.com \
--cc=spdawson@gmail.com \
--cc=thomas.petazzoni@bootlin.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