I fetched and updated master in linux-yocto-3.0 and cherry picked this into yocto/base, and merged it out. e6625fa..55f9c40 master -> master 935b896..c33fc74 yocto/base -> yocto/base

Nitin, Khem, some toolchain related (I think) questions inline below. In case you're actually curious :-) it's your mail client. It inserts the following header: In-Reply-To:

Bruce, Please apply to yocto/base. Fixes a boot issue for a tunnel creek development board. -- commit 2b934c6236983392d01bef22e43af3051cac16f5 If dmi_get_system_info() returns NULL,

Hi Darren - Thanks for getting back to me. I have been able to get a lot further with the recipe. It turns out that the problem is in the makefiles for OpenDDS. I'll detail further below. Paul E.

Hi Paul, This is the right place. In the future please don't reply to an existing post as your message then gets threaded with the one you replied to (likely why you didn't receive a response so far

Ok, maybe we want: -PACKAGE_ARCHS = "all any noarch ${PACKAGE_EXTRA_ARCHS} ${MACHINE_ARCH}" +PACKAGE_ARCHS = "all any noarch ${TUNE_PKGARCH} ${PACKAGE_EXTRA_ARCHS} ${MACHINE_ARCH}" instead as we

It isn't totally obvious to me that it needs to be an error for PACKAGE_ARCHS to contain dupes. AFAIK there is no reason that it couldn't simply be uniquified before use. p.

this change causes ERROR here with nokia900: Error, the PACKAGE_ARCHS variable contains duplicates. The following archs are listed more than once: armv7a-vfp-neon Regards, -- Martin 'JaMa' Jansa

so in conf/bitbake.conf PACKAGE_ARCH = "${TUNE_PKGARCH}" MACHINE_ARCH = "${@[bb.data.getVar('TUNE_PKGARCH', d, 1), bb.data.getVar('MACHINE', d, 1)][bool(bb.data.getVar('MACHINE', d, 1))].replace('-',

Why do we let the host perl in the path for target installs at all? Is there some precedence for what can be used from the host machine and what can not? -M

I have, it doesn't help. I believe its partly due to how we are appending to TUNE_PKGARCH, but what's not clear to me is what case is failing and looking for just ppc603e instead of powerpcppc603e -

This might also be related to the PACKAGE_EXTRA_ARCHS issue, please try the patch that Koen posted. Thanks Sau!

I think I know the cause, let me dig up the change that is related. What bit is looking for just ppc603e? - k

Hi Kumar, I'm just debugging the same issue. It's caused by folder for the target specific packages being mis-named "powerpcppc603e" instead of "ppc603e" which the rpm package bbclass is expecting.

Anyone got any ideas about the following: | ERROR: Function 'do_rootfs' failed (see

It seems like there is a way to use a prebuilt toolchain with poky but no real details. Some refs in the docs like: POKYMODE Toolchain selector. It can be external toolchain built from Poky or few

Matthew, Thanks for submitting this. A similar fix was recently rejected, as we are looking at a different way to accomplish this. See

Is it normal that the first stage (native) portion does not seem to either deal with BB_NUMBER_THREADS or PARALLEL_MAKE? - k

Saul has not woken up completely yet and thought that Paul made that change, thanks for speaking up! Sau!

Agreed, patch merged to master, thanks. Richard