On Fri, Nov 22, 2013 at 9:04 AM, Mike Crowe <m...@mcrowe.com> wrote:
> This reverts commit 3baa63b4d588c3262254528b406ede265dd117bf. It broke
> builds that aren't using kernel-yocto.
Can we get a log message of the breakage in the commit ? And a follow up
question, have we simply restored the issue that the original commit was
fixing ?
Bruce
>
> Signed-off-by: Mike Crowe <mcr...@brightsign.biz>
> ---
> 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 48999fe..ba13e67 100644
> --- a/meta/classes/kernel.bbclass
> +++ b/meta/classes/kernel.bbclass
> @@ -152,7 +152,7 @@ python do_devshell_prepend () {
> os.environ["LDFLAGS"] = ''
> }
>
> -addtask bundle_initramfs after do_kernel_link_vmlinux before do_build
> +addtask bundle_initramfs after do_compile before do_build
>
> kernel_do_compile() {
> unset CFLAGS CPPFLAGS CXXFLAGS LDFLAGS MACHINE
> --
> 1.7.10.4
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
