From: Joshua G Lock <joshua.g.lock@linux.intel.com>
To: yocto@yoctoproject.org
Subject: Re: Nettle from release Fido fails to build
Date: Fri, 11 Mar 2016 13:40:39 +0000 [thread overview]
Message-ID: <1457703639.7305.4.camel@linux.intel.com> (raw)
In-Reply-To: <56E298F0.50200@konsulko.com>
On Fri, 2016-03-11 at 12:07 +0200, Leon Anavi wrote:
> On 11.03.2016 11:50, Burton, Ross wrote:
> > On 11 March 2016 at 09:45, Leon Anavi <leon.anavi@konsulko.com>
> > wrote:
> > >
> > > Yesterday I noticed that the build of recipe nettle 2.7.1 from
> > > release Fido fails:
> > > https://gist.github.com/leon-anavi/dfd3afab567a9dc9fa2f
> > >
> > Theres a patch from a few days ago on this list to fix the issue: h
> > ttp://patchwork.openembedded.org/patch/117355/.
> >
> OK, thank you for the feedback. I will wait for the fix in the Poky
> repository.
This fix has now been merged to the fido branch of the poky repository.
Regards,
Joshua
next prev parent reply other threads:[~2016-03-11 13:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 9:45 Nettle from release Fido fails to build Leon Anavi
2016-03-11 9:50 ` 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 [this message]
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=1457703639.7305.4.camel@linux.intel.com \
--to=joshua.g.lock@linux.intel.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.