From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2,1/1] package/efivar: needs threads
Date: Sun, 05 Mar 2023 18:34:19 +0100 [thread overview]
Message-ID: <877cvv85lw.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20230223162847.9247-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Thu, 23 Feb 2023 17:28:47 +0100")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> 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
Committed to 2022.11.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-03-05 17: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
2023-03-05 17:34 ` Peter Korsgaard [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=877cvv85lw.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.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.