From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@gmail.com>,
"Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/7] linux-yocto: consolidated (and hopefully final) pull request
Date: Mon, 03 Oct 2016 23:09:18 +0100 [thread overview]
Message-ID: <1475532558.30475.338.camel@linuxfoundation.org> (raw)
In-Reply-To: <CADkTA4OTjXYScwAfUdjM8-LcRqbbX9g50OJ9ZAqfy+KDEF-nbQ@mail.gmail.com>
On Mon, 2016-10-03 at 12:55 -0400, Bruce Ashfield wrote:
>
>
> On Mon, Oct 3, 2016 at 12:07 PM, Bruce Ashfield <bruce.ashfield@gmail
> .com> wrote:
> >
> >
> > On Mon, Oct 3, 2016 at 12:03 PM, Burton, Ross <ross.burton@intel.co
> > m> wrote:
> > >
> > > On 3 October 2016 at 16:57, Bruce Ashfield <bruce.ashfield@gmail.
> > > com> wrote:
> > > > Out of curiosity, what image type is this ? built core-image-
> > > > sato, kernel-dev for
> > > > x86-64 and they all worked.
> > > >
> > > net-tools (via core-image-full-cmdline -c populate_sdk) for
> > > intel-corei7-64.
> > >
> >
> > ok. I've reproduced the failure by building just that package, with
> > any luck I can spin
> > something for it in the next few minutes and then launch a full
> > build of that image.
> >
> >
> patch sent. I can now build net-tools, and I launched a full build of
> core-image-full-cmdline.
> The clock is ticking on me now .. but I'll be around for another hour
> to monitor things.=
I've been running builds and it seems things are looking much greener
now FWIW!
Cheers,
Richard
prev parent reply other threads:[~2016-10-03 22:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-03 5:54 [PATCH 0/7] linux-yocto: consolidated (and hopefully final) pull request Bruce Ashfield
2016-10-03 5:54 ` [PATCH 1/7] linux-yocto/4.8: mmc configuration for x86* Bruce Ashfield
2016-10-03 5:54 ` [PATCH 2/7] linux-yocto/4.1: update to 4.1.33 Bruce Ashfield
2016-10-03 5:54 ` [PATCH 3/7] linux-yocto/4.4: update to v4.4.22 Bruce Ashfield
2016-10-03 5:54 ` [PATCH 4/7] linux-yocto/4.1/4.4: remove innappropriate standard/base patches Bruce Ashfield
2016-10-03 5:54 ` [PATCH 5/7] linux-libc-headers: update to 4.8 final Bruce Ashfield
2016-10-03 5:54 ` [PATCH 6/7] linux-yocto/4.8: update to 4.8 -final release Bruce Ashfield
2016-10-03 5:54 ` [PATCH 7/7] linux-libc-headers: fix in/if.h includes Bruce Ashfield
2016-10-03 15:45 ` [PATCH 0/7] linux-yocto: consolidated (and hopefully final) pull request Burton, Ross
2016-10-03 15:51 ` Bruce Ashfield
2016-10-03 15:57 ` Bruce Ashfield
2016-10-03 16:02 ` Bruce Ashfield
2016-10-03 16:03 ` Burton, Ross
2016-10-03 16:07 ` Bruce Ashfield
2016-10-03 16:55 ` Bruce Ashfield
2016-10-03 22:09 ` Richard Purdie [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=1475532558.30475.338.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox