From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>,
"Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] mesa: upgrade 10.6.3 -> 11.1.1
Date: Sun, 14 Feb 2016 14:37:50 +0000 [thread overview]
Message-ID: <1455460670.16142.408.camel@linuxfoundation.org> (raw)
In-Reply-To: <20160214115245.GC3028@jama>
On Sun, 2016-02-14 at 12:52 +0100, Martin Jansa wrote:
> On Tue, Feb 09, 2016 at 10:26:43PM +0000, Burton, Ross wrote:
> > On 8 February 2016 at 14:59, Nicolas Dechesne <
> > nicolas.dechesne@linaro.org>
> > wrote:
> >
> > > * update SRC_URI and checksum.
> > > * add PACKAGECONFIG to offer choice of crypto implementation (for
> > > sha1
> > > functions)
> > > * use libcrypto by default. In upstream commit a24bdce4, support
> > > for
> > > SHA-1 was copied from xserver repo, so let's use the same
> > > default for
> > > --with-sha1 option that we use in xserver recipe in OE core.
> > >
> >
> > Forgot to ask - what real hardware was this tested on, and was
> > anything
> > like Piglit used to verify it is working properly?
>
> It looks like non-x11 builds gained X11 dependency and mesa fails to
> build in DISTROs without x11 in DISTRO_FEATURES:
>
> mesa-11.1.1/src/loader/loader_dri3_helper.c:28:27: fatal error:
> X11/xshmfence.h: No such file or directory
I did test this recently:
https://autobuilder.yoctoproject.org/main/builders/nightly-no-x11/build
s/23/steps/BuildImages/logs/stdio
which uses mesa 11.1.1 and didn't see an issue. I therefore suspect
there is a bit more to the exact configuration needed to reproduce
this.
Cheers,
Richard
next prev parent reply other threads:[~2016-02-14 14:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 14:59 [PATCH v2] mesa: upgrade 10.6.3 -> 11.1.1 Nicolas Dechesne
2016-02-09 22:26 ` Burton, Ross
2016-02-09 22:54 ` Nicolas Dechesne
2016-02-14 11:52 ` Martin Jansa
2016-02-14 14:37 ` Richard Purdie [this message]
2016-02-15 21:45 ` Burton, Ross
2016-02-15 23:15 ` Martin Jansa
2016-02-16 9:20 ` Burton, Ross
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=1455460670.16142.408.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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