From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] classes/sanity: fix handling of bblayers.conf updating
Date: Wed, 17 Apr 2013 00:25:14 +0100 [thread overview]
Message-ID: <3552064.n2jxC3Or99@helios> (raw)
In-Reply-To: <20130416214108.GD29302@jama.dyndns-home.com>
On Tuesday 16 April 2013 23:41:08 Martin Jansa wrote:
> On Tue, Apr 16, 2013 at 10:06:06PM +0100, Richard Purdie wrote:
> > On Tue, 2013-04-16 at 19:09 +0200, Martin Jansa wrote:
> > > OK, so it's different than hangs I'm seeing here, because I'm still
> > > seeing them with latest oe-core>
> > Yes, that was almost certainly a different issue.
> >
> > > $ . ./oe-init-bitbake-build-env && bitbake my-image
> > > Altered environment for machine@distro development (this is from
> > > oe-init-bitbake-build-env) # and nothing else is shown after that
> >
> > So just to ensure I understand this, it never prints any messages at
> > all?
>
> yes nothing at all from bitbake, only that echo from setup script
> (oe-init-bitbake-build-env)
Are you sure it's not getting stuck doing a fetch as a result of a non-fully-
specified SRCREV?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-04-16 23:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 20:16 [PATCH 0/1] Fix handling of bblayers.conf updating Paul Eggleton
2013-04-12 20:16 ` [PATCH 1/1] classes/sanity: fix " Paul Eggleton
2013-04-12 21:10 ` Martin Jansa
2013-04-12 21:30 ` Richard Purdie
2013-04-16 17:09 ` Martin Jansa
2013-04-16 21:06 ` Richard Purdie
2013-04-16 21:41 ` Martin Jansa
2013-04-16 23:25 ` Paul Eggleton [this message]
2013-04-17 7:01 ` Richard Purdie
2013-04-17 8:54 ` Martin Jansa
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=3552064.n2jxC3Or99@helios \
--to=paul.eggleton@linux.intel.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox