All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>,
	"Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/8] Extensible SDK improvements
Date: Fri, 29 Jul 2016 08:26:13 +0100	[thread overview]
Message-ID: <1469777173.9142.50.camel@linuxfoundation.org> (raw)
In-Reply-To: <1948585.XiSYCAuUde@peggleto-mobl.ger.corp.intel.com>

On Mon, 2016-07-25 at 19:42 +1200, Paul Eggleton wrote:
> On Sat, 23 Jul 2016 13:11:39 Paul Eggleton wrote:
> > On Fri, 22 Jul 2016 23:31:38 Burton, Ross wrote:
> > > On 22 July 2016 at 13:38, Paul Eggleton <
> > > paul.eggleton@linux.intel.com>
> > > 
> > > wrote:
> > > > Some fixes and enhancements centered around how the toolchain
> > > > is
> > > > incorporated in the eSDK, as well as a couple of tweaks for
> > > > buildhistory
> > > > that I found we needed during development.
> > > 
> > > This is happening in mut, could your branch be responsible:
> > > 
> > > http://errors.yoctoproject.org/Errors/Details/73022/
> > > 
> > > Ross (who will look further when its not 23:30 on Friday!)
> > 
> > Hmm, it will be, but I can't tell immediately from the error
> > message what
> > could be wrong...
> 
> Ah, I believe this is bash vs. dash. Fix incoming, just need to test
> it.

Thanks for that fix. I think but am not 100% sure that this patchset
may have also caused:

https://autobuilder.yoctoproject.org/main/builders/nightly-oecore/build
s/865

which happens only on OE-Core testing :/.

Cheers,

Richard


  reply	other threads:[~2016-07-29  7:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-22 12:38 [PATCH 0/8] Extensible SDK improvements Paul Eggleton
2016-07-22 12:38 ` [PATCH 1/8] classes/populate_sdk_ext: set default for SDK_INCLUDE_PKGDATA Paul Eggleton
2016-07-22 12:38 ` [PATCH 2/8] meta-extsdk-toolchain: add meta-recipe to install toolchain into eSDK Paul Eggleton
2016-07-22 12:38 ` [PATCH 3/8] classes/populate_sdk_ext: allow including toolchain in eSDK on install Paul Eggleton
2016-07-22 12:38 ` [PATCH 4/8] scripts: add oe-check-sstate script Paul Eggleton
2016-07-22 12:38 ` [PATCH 5/8] classes/populate_sdk_ext: filter sstate within the extensible SDK Paul Eggleton
2016-07-25  8:41   ` [PATCH v2] " Paul Eggleton
2016-07-22 12:38 ` [PATCH 6/8] classes/populate_sdk_ext: add gdb to full " Paul Eggleton
2016-07-22 12:38 ` [PATCH 7/8] classes/buildhistory: add additional variables for eSDK Paul Eggleton
2016-07-22 12:38 ` [PATCH 8/8] classes/buildhistory: ensure eSDK sstate lists sorted secondarily by name Paul Eggleton
2016-07-22 22:31 ` [PATCH 0/8] Extensible SDK improvements Burton, Ross
2016-07-23  1:11   ` Paul Eggleton
2016-07-24 21:42     ` Paul Eggleton
2016-07-24 23:31       ` Khem Raj
2016-07-24 23:45         ` Paul Eggleton
2016-07-25 16:39       ` Burton, Ross
2016-07-25 20:33         ` Paul Eggleton
2016-07-25 20:38           ` Burton, Ross
2016-07-25  7:42     ` Paul Eggleton
2016-07-29  7:26       ` Richard Purdie [this message]
2016-07-30 10:01         ` Paul Eggleton
2016-08-01  1:35           ` Paul Eggleton

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=1469777173.9142.50.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    --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 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.