[OE-core] [RESEND PATCH] mesa: upgrade 10.6.3 -> 11.1.1

[Jussi Kukkonen]

On 5 February 2016 at 22:55, Nicolas Dechesne <nicolas.dechesne at linaro.org>
wrote:

> On Fri, Feb 5, 2016 at 9:46 PM, Burton, Ross <ross.burton at intel.com>
> wrote:
> > On 5 February 2016 at 20:44, Khem Raj <raj.khem at gmail.com> wrote:
> >>
> >> its added new to this version. May be packageconfig is better place
> >> for --with-sha1 stuff
> >
> >
> > Agreed - some may not want openssl at all and being able to switch it for
> > another alternative would be useful.
>
> sure. but, then I have some questions..
>
> 1. which one we default to? openssl?
>
> 2. which one we support, from configure.ac:
>
>         [choose SHA1 implementation])])
> case "x$with_sha1" in
> x | xlibc | xlibmd | xlibnettle | xlibgcrypt | xlibcrypto | xlibsha1 |
> xCommonCrypto | xCryptoAPI)
>   ;;
>

Thanks for looking at this -- I was updating mesa last week as well and
fell into the same maze of crypto choices, all alike. Currently OE-Core is
pretty unorganized here: It's easy to end up with three big libraries just
for calculating SHA1 hashes.

If you do this patch for mesa, I'll follow up with one for xorg: we should
at least default to the same choice. Currently Xorg uses libcrypto for
SHA1, I think that's reasonable for mesa as well? As Andre said, the
maintained version of Nettle has the problem of being "LGPL3|GPLv2".

In addition there's quite a few unneeded crypto dependencies that I intend
to remove: It's possible that with some smart choices we may be able to
drop some libraries from the core images (see
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=jku/mesa-update
for a start).

If you don't have time to do the mesa-packageconfig patch, let me know and
I'll do it.

Jussi

3. is there a good way to handle 'multiple choice' with PACKAGECONFIG?
> How can we prevent more than 1 PACKAGECONFIG to be set (nicely)?
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20160208/fb499833/attachment-0002.html>