From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libcgroup: needs threads
Date: Tue, 2 Jan 2024 23:20:11 +0100 [thread overview]
Message-ID: <20240102232011.5fdc0384@windsurf> (raw)
In-Reply-To: <20240102210751.1676704-1-fontaine.fabrice@gmail.com>
On Tue, 2 Jan 2024 22:07:51 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> threads are mandatory since the addition of the package in commit and
> https://github.com/libcgroup/libcgroup/commit/99ccdf671e9df5b13f646e1487393d562aa7fa62
> resulting in the following build failure since commit
> 9d58b525fcfd0d92fcdd3c66d7858213c4b139c6 which enables build on uclibc
> and musl:
>
> In file included from config.c:30:
> ./libcgroup-internal.h:29:10: fatal error: pthread.h: No such file or directory
> 29 | #include <pthread.h>
> | ^~~~~~~~~~~
>
> Fixes:
> - http://autobuild.buildroot.org/results/87c4454aee97b6955f461651c41c4186a8838c4d
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/libcgroup/Config.in | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
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-01-02 22:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 21:07 [Buildroot] [PATCH 1/1] package/libcgroup: needs threads Fabrice Fontaine
2024-01-02 22:20 ` Thomas Petazzoni via buildroot [this message]
2024-01-12 17:18 ` Peter Korsgaard
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=20240102232011.5fdc0384@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@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