[Angstrom-devel] A couple of questions

[AsLan^]

It was indeed qemu-native, thank you for pointing me in the direction  
of the patch (and other advice) which worked as described.

Sincerely,

Fredrick Pennachi

On May 13, 2007, at 1:47 PM, Junqian Gordon Xu wrote:

> AsLan^ wrote:
>> It seems like there's a lot of tasks to build even a single package.
>> When I type "bitbake nano" for example, there is 294 tasks that need
>> to be completed by bitbake. Is this normal?
>>
> Yes it is normal.
>> And bitbake angstrom-x11-image show something like 3000 tasks that
>> need to be completed. I'm not really used to such long build times,
>> and I don't understand the development process.
> My understanding is that OE is a meta-building environment, sort of
> cross-compiling-from-scratch. So it needs to build a lot of basic
> libraries and binaries in both native and cross environment.
>> I wanted to try and
>> find the bug affecting the suspend/resume problems we have on Tosa
>> but now I'm quite lost.
>>
> It's likely a kernel bug. Hrw knows more.
>> I also tried building the angstrom-console-image and it failed after
>> a 160 tasks or so (with something like 900 remaining) after it had
>> been going for about an hour. I don't recall which package it was but
>> I think it was qemu or bochs (or something like that) which didn't
>> seem especially relevant to a zaurus image.
> If it's qemu-native, try the patch in bug 2157. That patch works great
> for me on i686 host machine.
>
>
> _______________________________________________
> Angstrom-distro-devel mailing list
> Angstrom-distro-devel at linuxtogo.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro- 
> devel