All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: "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 12:52:45 +0100	[thread overview]
Message-ID: <20160214115245.GC3028@jama> (raw)
In-Reply-To: <CAJTo0LZm-Q-f8im1Ssfcp6z8T2nj51ToV=s9NMYF2EP0z-Yt4Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1161 bytes --]

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


> 
> Ross

> -- 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core


-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  parent reply	other threads:[~2016-02-14 11:48 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 [this message]
2016-02-14 14:37     ` Richard Purdie
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=20160214115245.GC3028@jama \
    --to=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 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.