From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Bernd Kuhls <bernd.kuhls@t-online.de>,
Louis-Paul Cordier <lpdev@cordier.org>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/intel-gmmlib: needs threads
Date: Sat, 25 Feb 2023 10:40:25 +0100 [thread overview]
Message-ID: <20230225104025.23e4e21c@windsurf> (raw)
In-Reply-To: <20230224164053.53287-1-fontaine.fabrice@gmail.com>
On Fri, 24 Feb 2023 17:40:53 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> threads are mandatory since version 19.1.1 and
> https://github.com/intel/gmmlib/commit/9e4aa143fb7e7e87332fcb7c9871040ff4a1a1da
> resulting in the following build failure since commit
> cd206d9b808a322a00294b4caad203a892ed4c92:
>
> CMake Error at /home/thomas/autobuild/instance-2/output-1/host/share/cmake-3.22/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
> Could NOT find Threads (missing: Threads_FOUND)
>
> Fixes:
> - http://autobuild.buildroot.org/results/c1120932e8c212820b239ee8cd4a057623a73376
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/intel-gmmlib/Config.in | 6 ++++--
> package/intel-mediadriver/Config.in | 2 +-
> 2 files changed, 5 insertions(+), 3 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:[~2023-02-25 9:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 16:40 [Buildroot] [PATCH 1/1] package/intel-gmmlib: needs threads Fabrice Fontaine
2023-02-25 9:40 ` Thomas Petazzoni via buildroot [this message]
2023-03-12 18:47 ` 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=20230225104025.23e4e21c@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd.kuhls@t-online.de \
--cc=fontaine.fabrice@gmail.com \
--cc=lpdev@cordier.org \
--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 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.