From: Martin Jansa <martin.jansa@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: penembedded-commits@lists.openembedded.org,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [oe-commits] [openembedded-core] 67/76: gnutls: update to 3.5.6
Date: Tue, 6 Dec 2016 16:01:55 +0100 [thread overview]
Message-ID: <20161206150155.GC3255@jama> (raw)
In-Reply-To: <CAJTo0LbaSgpFSthT55QFroQ8Uc51x4KpOUK8GZK-8=NCf8oE8Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]
On Tue, Dec 06, 2016 at 02:47:42PM +0000, Burton, Ross wrote:
> On 6 December 2016 at 14:44, Martin Jansa <martin.jansa@gmail.com> wrote:
>
> > Probably caused by nettle upgrade which no longer enables gmp with older
> > gmp 4.2.1 used in non-GPLv3 builds.
> >
>
> I was going to say I don't see this. Clearly we need to extend the
> non-GPL3 testing.
>
> As you can reproduce this, is there a simple fix?
Restoring nettle-3.2 (which got replaced with 3.3 in this commit:
commit fc37c0787008437d94bccfaa91d0b84180a393c9
Author: Fabio Berton <fabio.berton@ossystems.com.br>
Date: Mon Nov 21 18:17:24 2016 -0200
nettle: Update to version 3.3
Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
Signed-off-by: Ross Burton <ross.burton@intel.com>
)
allows to use gmp-4.2.1 and nettle-3.2 is good enough for
gnutls.do_configure.
Now I need to check if LGPLv3 libnettle or libhogweed end in the image
or not.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
prev parent reply other threads:[~2016-12-06 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161130154845.8882.9798@opal.openembedded.org>
[not found] ` <20161130154913.0EEAE50166@opal.openembedded.org>
2016-12-06 13:49 ` [oe-commits] [openembedded-core] 67/76: gnutls: update to 3.5.6 Martin Jansa
2016-12-06 14:44 ` Martin Jansa
2016-12-06 14:47 ` Burton, Ross
2016-12-06 15:01 ` Martin Jansa [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=20161206150155.GC3255@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=penembedded-commits@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