All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: The rpurdie/work-in-progress branch has been merged
Date: Thu, 06 May 2010 14:48:05 +0200	[thread overview]
Message-ID: <hrudq5$vms$1@dough.gmane.org> (raw)
In-Reply-To: <1273147827.5743.104.camel@rex>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 06-05-10 14:10, Richard Purdie wrote:
> On Thu, 2010-05-06 at 09:03 +0200, Koen Kooi wrote:
>> On 06-05-10 08:23, Koen Kooi wrote:
>>> On 06-05-10 01:43, Richard Purdie wrote:
>>>> I finally felt the time was right so I've merged the work-in-progress
>>>> branch I've been talking about to OE.dev. This contains various
>>>> architecture improvements and legacy staging cleanups that have been
>>>> used in Poky for a while with great benefit.
>>>
>>> With bitbake 1.10 I get:
>>>
>>> NOTE: Preparing runqueue
>>> Traceback (most recent call last):
>>>   File "/OE/bitbake/lib/bb/server/none.py", line 128, in idle_commands
>>>     retval = function(self, data, False)
>>>   File "/OE/bitbake/lib/bb/cooker.py", line 730, in buildTargetsIdle
>>>     retval = rq.execute_runqueue()
>>>   File "/OE/bitbake/lib/bb/runqueue.py", line 830, in execute_runqueue
>>>     self.prepare_runqueue()
>>>   File "/OE/bitbake/lib/bb/runqueue.py", line 513, in prepare_runqueue
>>>     if len(runq_recrdepends[task]) > 0:
>>> IndexError: list index out of range
>>>
>>> when doing MACHINE=beagleboard bitbake console-image
>>
>> Bitbake 1.8, 1.10 and master exhibit the same behaviour. 'bitbake gcc'
>> does work, trying to narrow down which recipe is causing this, it's not
>> the toolchain.
> 
> Someone just told me OE was broken as this email hadn't been replied
> too. For reference, Koen and I talked elsewhere, a fix was pushed and
> this issue was resolved. 

I have built console-image for hawkboard, smartq5 and beagleboard and
they all work as well as before. Thanks to the removal of legacy staging
in gcc, glibc, etc, the build was a bit faster (but still dominated by
localegen).

> To further update, Khem pushed updates for eglibc and gcc 4.5 (thanks).
> Koen also pushed some legacy staging removals which had some issues but
> these have also all been fixed.

Note to self: if something doesn't use 'make install', it needs
'NATIVE_INSTALL_WORKS = 1' when using BBCLASSEXTEND = native.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFL4rqFMkyGM64RGpERAotJAJ4+LvJTHsPCfhRPcYCmHRYbzgo/5gCeKBvz
VKoBx4YqEtsQiONmXlDxBQ8=
=5V/p
-----END PGP SIGNATURE-----




  reply	other threads:[~2010-05-06 12:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-05 23:43 The rpurdie/work-in-progress branch has been merged Richard Purdie
2010-05-06  0:14 ` Tom Rini
2010-05-06  1:29   ` Khem Raj
2010-05-06 19:52   ` Tom Rini
2010-05-07  1:17     ` Khem Raj
2010-05-07 16:13       ` Tom Rini
2010-05-07 21:37         ` Andrea Adami
2010-05-07 21:57           ` Andrea Adami
2010-05-07 22:12             ` Andrea Adami
2010-05-06  6:11 ` Koen Kooi
2010-05-06  6:23 ` Koen Kooi
2010-05-06  7:03   ` Koen Kooi
2010-05-06 12:10     ` Richard Purdie
2010-05-06 12:48       ` Koen Kooi [this message]
2010-05-07  7:26         ` Michael Lippautz
2010-05-06 12:55       ` Martin Jansa
2010-05-06  6:38 ` Koen Kooi
2010-05-06  7:14   ` Khem Raj

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='hrudq5$vms$1@dough.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@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 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.