From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Devoogdt <thomas@devoogdt.com>
Cc: Adrian Perez de Castro <aperez@igalia.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1] package/libgtk4: fix execinfo compile error
Date: Thu, 5 Sep 2024 22:45:41 +0200 [thread overview]
Message-ID: <20240905224541.4b62638c@windsurf> (raw)
In-Reply-To: <20240831113626.105125-2-thomas@devoogdt.com>
On Sat, 31 Aug 2024 13:36:26 +0200
Thomas Devoogdt <thomas@devoogdt.com> wrote:
> ../testsuite/reftests/gtk-reftest.c:28:10: fatal error: execinfo.h: No such file or directory
>
> We don't need the test suite, so disable it.
>
> Signed-off-by: Thomas Devoogdt <thomas@devoogdt.com>
> ---
> package/libgtk4/libgtk4.mk | 1 +
> 1 file changed, 1 insertion(+)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-09-05 20:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-31 11:36 [Buildroot] [PATCH v1] package/webkitgtk: add libgtk4 support Thomas Devoogdt
2024-08-31 11:36 ` [Buildroot] [PATCH v1] package/libgtk4: fix execinfo compile error Thomas Devoogdt
2024-09-05 20:45 ` Thomas Petazzoni via buildroot [this message]
2024-09-17 20:32 ` [Buildroot] [PATCH v2] package/webkitgtk: add libgtk4 support Thomas Devoogdt
2024-12-16 18:10 ` [Buildroot] [PATCH v3] " Thomas Devoogdt
2025-04-20 7:36 ` [Buildroot] [PATCH v4] " Thomas Devoogdt
2025-05-18 13:40 ` Thomas Petazzoni via buildroot
2025-05-31 16:38 ` [Buildroot] [PATCH v1] " Arnout Vandecappelle via buildroot
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=20240905224541.4b62638c@windsurf \
--to=buildroot@buildroot.org \
--cc=aperez@igalia.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=thomas@devoogdt.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