On 06/13/2011 11:31 AM, Koen Kooi wrote:
Hi,
Khem was asking if I could reproduce the recent x86 breakage he was seeing[1]
and I ran into another bug:
koen@dominion:/OE/tentacle/sources/meta-intel$ git blame
meta-n450/conf/machine/n450.conf | grep atom
158f88d7 (Saul Wold 2011-01-03 15:33:52 -0800 6) require
conf/machine/atom-pc.conf
meta-yocto seems to be the place you need to look!
I hope that the layering tools can help to detect and inform folks of
this like of dependency.
Sau!
(yes another tentacle to keep track of!)
koen@dominion:/OE/tentacle/sources/meta-intel$ !find
find . -name "atom-pc.conf"
koen@dominion:/OE/tentacle/sources/meta-intel$
So let's drop down a level and try other layers:
koen@dominion:/OE/tentacle/sources/meta-intel$ cd ..
koen@dominion:/OE/tentacle/sources$ ls -1 | grep meta
meta-angstrom/
meta-efikamx/
meta-intel/
meta-nslu2/
meta-openembedded/
meta-openpandora/
meta-shr/
meta-smartphone/
meta-texasinstruments/
meta-xilinx/
koen@dominion:/OE/tentacle/sources$ find . -name "atom-pc.conf"
koen@dominion:/OE/tentacle/sources$
Still nothing. So where is it hiding?
regards,
Koen
[1] The bugs:
20:22<khem> MACHINE=4 bitbake console-image
20:22<khem> try any nonexisting machine
20:22<khem> no error nothing
and:
20:23<khem> so any x86 arch in angstrom is not parsable
20:23<khem> and it seems to be culminating from various factors
20:24<khem> if I remove inheriting rm_work it starts to work
20:24<khem> if I remove BASE_PACKAGE_ARCH = "all" from allarch.bbclass it
starts to work
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
