From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2,1/1] package/efivar: needs threads
Date: Thu, 23 Feb 2023 23:34:45 +0100 [thread overview]
Message-ID: <20230223233445.47f2a4af@windsurf> (raw)
In-Reply-To: <20230223162847.9247-1-fontaine.fabrice@gmail.com>
On Thu, 23 Feb 2023 17:28:47 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Add a thread dependency as Upstream quickly closed
> https://github.com/rhboot/efivar/pull/238 to fix the following build
> failure without threads raised since bump to version 38 in commit
> f24029b561fbda0953c7dbd93d2485b03873996d and
> https://github.com/rhboot/efivar/commit/cff88dd96b9d43e2c5875a24ba6180b196890ded:
>
> thread-test.c:14:10: fatal error: pthread.h: No such file or directory
> 14 | #include <pthread.h>
> | ^~~~~~~~~~~
>
> Fixes:
> - http://autobuild.buildroot.org/results/f2da14f91dc602a32dd5b2b7bdf3d3aa43afa7f4
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> Changes v1 -> v2:
> - Add a thread dependency
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:[~2023-02-23 22:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 16:28 [Buildroot] [PATCH v2,1/1] package/efivar: needs threads Fabrice Fontaine
2023-02-23 22:34 ` Thomas Petazzoni via buildroot [this message]
2023-03-05 17:34 ` 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=20230223233445.47f2a4af@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