On Tue, 2015-07-21 at 15:23 +0800, zhe...@windriver.com wrote:
> From: He Zhe <zhe...@windriver.com>
>
> Pass mkimage in sysroot to kernel makefile by NATIVE_MKIMAGE to avoid
> depending on build machine's when KEEPUIMAGE is "yes".
>
> Fixes [YOCTO #6945].
>
> Signed-off-by: He Zhe <zhe...@windriver.com>
> ---
> meta/classes/kernel.bbclass | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
> index 86ed28f..1d7fa48 100644
> --- a/meta/classes/kernel.bbclass
> +++ b/meta/classes/kernel.bbclass
> @@ -141,7 +141,7 @@ UBOOT_ENTRYPOINT ?= "20008000"
> UBOOT_LOADADDRESS ?= "${UBOOT_ENTRYPOINT}"
>
> # Some Linux kernel configurations need additional parameters on the command
> line
> -KERNEL_EXTRA_ARGS ?= ""
> +KERNEL_EXTRA_ARGS ?= "NATIVE_MKIMAGE=${STAGING_BINDIR_NATIVE}/mkimage"
>
> # For the kernel, we don't want the '-e MAKEFLAGS=' in EXTRA_OEMAKE.
> # We don't want to override kernel Makefile variables from the environment
${STAGING_BINDIR_NATIVE} should be in PATH ahead of the usual system
paths. Why therefore is this necessary? Is something resetting PATH?
Cheers,
Richard
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
