From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] kernel.bbclass, base.bbclass: Fix support for old kernel configuration
Date: Wed, 12 Feb 2014 09:01:04 -0700 [thread overview]
Message-ID: <52FB9AC0.3020108@mlbassoc.com> (raw)
In-Reply-To: <1392220457-23287-1-git-send-email-otavio@ossystems.com.br>
On 2014-02-12 08:54, Otavio Salvador wrote:
> This solves a regression introduced by OE-Core:9b75f6a (kernel:
> use oldnoconfig before yes '' | make oldconfig).
>
> The original oe_runmake explicitly calls 'die' command in case of
> failure so the fallback code never runs. The fallback code needs
> to handle the oe_runmake return code to call the backward
> compatible callback so we introduced a new command called
> oe_runmake_call which is used by oe_runmake.
>
> This does not change the functional behaviour of oe_runmake so it
> avoids any change except for the code which does need to handle
> the oe_runmake exit code.
>
> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
You might make it clear in this description that this change is necessary
to handle older kernels where 'make oldnoconfig' is not supported.
> ---
> meta/classes/base.bbclass | 8 ++++++--
> meta/classes/kernel.bbclass | 2 +-
> 2 files changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/meta/classes/base.bbclass b/meta/classes/base.bbclass
> index 81fc305..7837c89 100644
> --- a/meta/classes/base.bbclass
> +++ b/meta/classes/base.bbclass
> @@ -53,9 +53,13 @@ die() {
> bbfatal "$*"
> }
>
> -oe_runmake() {
> +oe_runmake_call() {
> bbnote ${MAKE} ${EXTRA_OEMAKE} "$@"
> - ${MAKE} ${EXTRA_OEMAKE} "$@" || die "oe_runmake failed"
> + ${MAKE} ${EXTRA_OEMAKE} "$@"
> +}
> +
> +oe_runmake() {
> + oe_runmake_call "$@" || die "oe_runmake failed"
> }
>
>
> diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
> index 3003fb1..6953109 100644
> --- a/meta/classes/kernel.bbclass
> +++ b/meta/classes/kernel.bbclass
> @@ -313,7 +313,7 @@ python sysroot_stage_all () {
> oe.path.copyhardlinktree(d.expand("${D}${KERNEL_SRC_PATH}"), d.expand("${SYSROOT_DESTDIR}${KERNEL_SRC_PATH}"))
> }
>
> -KERNEL_CONFIG_COMMAND ?= "oe_runmake oldnoconfig || yes '' | oe_runmake oldconfig"
> +KERNEL_CONFIG_COMMAND ?= "oe_runmake_call oldnoconfig || yes '' | oe_runmake oldconfig"
>
> kernel_do_configure() {
> # fixes extra + in /lib/modules/2.6.37+
>
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2014-02-12 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 15:54 [PATCH] kernel.bbclass, base.bbclass: Fix support for old kernel configuration Otavio Salvador
2014-02-12 16:01 ` Gary Thomas [this message]
2014-02-12 16:29 ` Alexandre Belloni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52FB9AC0.3020108@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox