From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio@ossystems.com.br>,
OpenEmbedded Core Mailing List
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] mesa: Upgrade to 17.2.1 release
Date: Thu, 21 Sep 2017 23:34:37 +0100 [thread overview]
Message-ID: <1506033277.18640.172.camel@linuxfoundation.org> (raw)
In-Reply-To: <20170921140819.21292-1-otavio@ossystems.com.br>
On Thu, 2017-09-21 at 11:08 -0300, Otavio Salvador wrote:
> Upgrade to a new stable release and drop patches applied on upstream.
>
> For a full release notes, please see:
> https://mesa3d.org/relnotes/17.2.0.html
> https://mesa3d.org/relnotes/17.2.1.html
>
> Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> ---
>
> Changes in v2:
> - update to 17.2.1
The trouble is this isn't just a "stable release", I didn't check the
patch fully enough initially but now I see this was a 17.1.X -> 17.2.X
change.
When I tried building it locally I get:
| checking for x11 xext xdamage >= 1.1 xfixes x11-xcb xcb xcb-glx >= 1.8.1 xcb-dri2 >= 1.8 xxf86vm... yes
| checking for wayland-scanner... /media/build1/poky/build/tmp/work/core2-64-poky-linux/mesa/2_17.2.1-r0/recipe-sysroot-native/usr/bin/wayland-scanner
| checking for wayland-client >= 1.11 wayland-server >= 1.11... yes
| configure: error: wayland-protocols >= 1.8 is needed to compile the wayland platform
| NOTE: The following config.log files may provide further information.
and basically I just wiped out a round of autobuilder testing of a
larger patchset due to this.
If people want us to be more flexible about taking "point version"
changes later into the release cycle, we really need to start getting
better about how these things get tested and how we refer to them in
the commit messages.
[and yes, the fix is trivial and included below, that isn't really the
point though]
Cheers,
Richard
diff --git a/meta/recipes-graphics/mesa/mesa.inc b/meta/recipes-graphics/mesa/mesa.inc
index 4f31ed255c3..cab8e4bfe73 100644
--- a/meta/recipes-graphics/mesa/mesa.inc
+++ b/meta/recipes-graphics/mesa/mesa.inc
@@ -45,7 +45,7 @@ X11_DEPS = "xf86driproto glproto virtual/libx11 libxext libxxf86vm libxdamage li
# "x11" requires "opengl"
PACKAGECONFIG[x11] = "--enable-glx-tls,--disable-glx,${X11_DEPS}"
PACKAGECONFIG[xvmc] = "--enable-xvmc,--disable-xvmc,libxvmc"
-PACKAGECONFIG[wayland] = ",,wayland-native wayland libdrm"
+PACKAGECONFIG[wayland] = ",,wayland-native wayland libdrm wayland-protocols"
next prev parent reply other threads:[~2017-09-21 22:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 14:08 [PATCH v2] mesa: Upgrade to 17.2.1 release Otavio Salvador
2017-09-21 22:34 ` Richard Purdie [this message]
2017-09-22 0:43 ` Otavio Salvador
2017-09-22 6:43 ` Richard Purdie
2017-09-22 13:30 ` Otavio Salvador
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=1506033277.18640.172.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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