From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libva-utils: fix non x11 build
Date: Fri, 10 Jan 2020 23:15:58 +0100 [thread overview]
Message-ID: <20200110231558.41c1dcd3@windsurf> (raw)
In-Reply-To: <20200106055116.149922-1-bernd.kuhls@t-online.de>
Hello Bernd,
On Mon, 6 Jan 2020 06:51:16 +0100
Bernd Kuhls <bernd.kuhls@t-online.de> wrote:
> Fixes:
> http://autobuild.buildroot.net/results/70f/70fd6609fffdaa07be583420dab067da27b7d505/
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> .../0001-fix-build-without-x11.patch | 33 +++++++++++++++++++
> package/libva-utils/libva-utils.mk | 2 ++
> 2 files changed, 35 insertions(+)
> create mode 100644 package/libva-utils/0001-fix-build-without-x11.patch
>
> diff --git a/package/libva-utils/0001-fix-build-without-x11.patch b/package/libva-utils/0001-fix-build-without-x11.patch
> new file mode 100644
> index 0000000000..905e90410f
> --- /dev/null
> +++ b/package/libva-utils/0001-fix-build-without-x11.patch
> @@ -0,0 +1,33 @@
> +From 5efef48d74d772cb5318345aa61d94d27e0c42d1 Mon Sep 17 00:00:00 2001
> +From: Lukas Rusak <lorusak@gmail.com>
> +Date: Fri, 22 Feb 2019 18:43:25 -0800
> +Subject: [PATCH] only build sfcsample when x11 is enabled
> +
> +Downloaded from https://github.com/LibreELEC/LibreELEC.tv/pull/4093
This link now says:
Upsteam fix seems to be intel/libva-utils at 82ccf0f
which points to https://github.com/intel/libva-utils/commit/82ccf0fc82ec3929e545fb06880b1ea955ef54ac
Could you try this one instead, since it has been merged upstream ?
(And it doesn't need autoreconf).
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2020-01-10 22:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 5:51 [Buildroot] [PATCH 1/1] package/libva-utils: fix non x11 build Bernd Kuhls
2020-01-10 22:15 ` Thomas Petazzoni [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=20200110231558.41c1dcd3@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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