All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: bitbake-devel@lists.openembedded.org,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] meta-micro problems
Date: Sat, 01 Oct 2011 22:00:01 +0400	[thread overview]
Message-ID: <4E875521.3000809@gmail.com> (raw)
In-Reply-To: <201109281432.57331.paul.eggleton@linux.intel.com>

On 09/28/2011 05:32 PM, Paul Eggleton wrote:
> On Wednesday 28 September 2011 13:51:52 Dmitry Eremin-Solenikov wrote:
>> If you wish, I can retry this with smaller layer set. But if the bug
>> will still arise, I simply have no knowledge/time to look deeper into bb
>> without additional input/pointers from bb gurus.
>
> That's OK, I can spend time looking into it. It sounds like a bug in bitbake
> if metadata can influence it to behave this way. If we can produce a simplified
> test case I think it will be easier to fix.

I have rechecked things on my test box, meta-micro still causes fails 
for me on rebuild. Setup:

I use setup-scripts from angstrom, change bblayers.conf to contain only 
oe-core and meta-micro, switched DISTRO to "micro", changed 
PARALLEL_MAKE to -j 4, BB_NUMBER_THREADS to 4, machine is qemuarm

Then:
1) bitbake pseudo-native succeeds
2) next bitbake pseudo-native fails. Usually in rm_work of any of the 
packages (automake-native,openssl-native,python-native are few to name).

-- 
With best wishes
Dmitry



WARNING: multiple messages have this Message-ID (diff)
From: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: bitbake-devel@lists.openembedded.org,
	openembedded-core@lists.openembedded.org
Subject: Re: meta-micro problems
Date: Sat, 01 Oct 2011 22:00:01 +0400	[thread overview]
Message-ID: <4E875521.3000809@gmail.com> (raw)
In-Reply-To: <201109281432.57331.paul.eggleton@linux.intel.com>

On 09/28/2011 05:32 PM, Paul Eggleton wrote:
> On Wednesday 28 September 2011 13:51:52 Dmitry Eremin-Solenikov wrote:
>> If you wish, I can retry this with smaller layer set. But if the bug
>> will still arise, I simply have no knowledge/time to look deeper into bb
>> without additional input/pointers from bb gurus.
>
> That's OK, I can spend time looking into it. It sounds like a bug in bitbake
> if metadata can influence it to behave this way. If we can produce a simplified
> test case I think it will be easier to fix.

I have rechecked things on my test box, meta-micro still causes fails 
for me on rebuild. Setup:

I use setup-scripts from angstrom, change bblayers.conf to contain only 
oe-core and meta-micro, switched DISTRO to "micro", changed 
PARALLEL_MAKE to -j 4, BB_NUMBER_THREADS to 4, machine is qemuarm

Then:
1) bitbake pseudo-native succeeds
2) next bitbake pseudo-native fails. Usually in rm_work of any of the 
packages (automake-native,openssl-native,python-native are few to name).

-- 
With best wishes
Dmitry



  parent reply	other threads:[~2011-10-01 18:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-16 18:17 meta-micro problems Dmitry Eremin-Solenikov
2011-09-28 10:16 ` [OE-core] " Paul Eggleton
2011-09-28 10:16   ` Paul Eggleton
2011-09-28 12:51   ` [OE-core] " Dmitry Eremin-Solenikov
2011-09-28 12:51     ` Dmitry Eremin-Solenikov
2011-09-28 13:32     ` [OE-core] " Paul Eggleton
2011-09-28 13:32       ` Paul Eggleton
2011-09-28 17:21       ` [OE-core] " Dmitry Eremin-Solenikov
2011-09-28 17:21         ` Dmitry Eremin-Solenikov
2011-09-28 18:56       ` [OE-core] " Dmitry Eremin-Solenikov
2011-09-28 18:56         ` Dmitry Eremin-Solenikov
2011-10-01 18:00       ` Dmitry Eremin-Solenikov [this message]
2011-10-01 18:00         ` Dmitry Eremin-Solenikov

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=4E875521.3000809@gmail.com \
    --to=dbaryshkov@gmail.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.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.