From: Leon Anavi <leon.anavi@konsulko.com>
To: yocto@yoctoproject.org
Subject: Nettle from release Fido fails to build
Date: Fri, 11 Mar 2016 11:45:33 +0200 [thread overview]
Message-ID: <56E293BD.1080009@konsulko.com> (raw)
Hi,
Yesterday I noticed that the build of recipe nettle 2.7.1 from release
Fido fails:
https://gist.github.com/leon-anavi/dfd3afab567a9dc9fa2f
The build machine is with Ubuntu 14.04 (Trusty Tahr). I am build Poky
with nettle for qemux86-64.
My investigation shows that nettle fails due to a couple of security
fixes (CVE-2015-8804, CVE-2015-8803 and CVE-2015-8805) which have been
applied to branch Fido recently:
https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-support/nettle/nettle_2.7.1.bb?h=fido#n13
The same patches are present in Jethro but the versions of nettle in
Jethro and Fido are different. The version in Fido is 2.7.1. Jethro has
recipes for both 2.7.1 and 3.1.1. As far as I can see in Jethro the
patches are applied only for version 3.1.1.Therefore in my opinion these
patches are for a newer versions of nettle and they are not compatible
with version 2.7.1 from release Fido.
Could you please have a look and let me know if I am doing something
wrong or if this is a bug that can be fixed for release Fido?
Best regards, Leon
--
Leon Anavi
Software Engineer
konsulko.com
next reply other threads:[~2016-03-11 9:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 9:45 Leon Anavi [this message]
2016-03-11 9:50 ` Nettle from release Fido fails to build Burton, Ross
2016-03-11 10:07 ` Leon Anavi
2016-03-11 10:20 ` Burton, Ross
2016-03-11 10:35 ` Leon Anavi
2016-03-11 13:40 ` Joshua G Lock
2016-03-11 13:43 ` Leon Anavi
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=56E293BD.1080009@konsulko.com \
--to=leon.anavi@konsulko.com \
--cc=yocto@yoctoproject.org \
/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.