From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <tom.zanussi@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] module.bbclass: make sure do_make_scripts() executes after do_patch()
Date: Fri, 14 Dec 2012 00:31:20 -0500 [thread overview]
Message-ID: <50CAB9A8.7010101@windriver.com> (raw)
In-Reply-To: <e7a95fde7267ebf9a1567d3f3aa1e459e12a5fea.1355462107.git.tom.zanussi@intel.com>
On 12-12-14 12:27 AM, tom.zanussi@intel.com wrote:
> From: Tom Zanussi<tom.zanussi@intel.com>
>
> If do_make_scripts() executes before do_unpack()/do_patch(), the build
> fails because it can't cd into the workdir of a recipe using this
> class, so make sure do_make_scripts() doesn't run before the package
> has been unpacked and patched.
I've never seen the problem myself, but having a more tightly defined
ordering for the task is a good thing in my books.
Since you aren't breaking the working use case, I have no objection.
So I'll throw out a fancy: Reviewed-by: Bruce Ashfield
<bruce.ashfield@windriver.com>
Cheers,
Bruce
>
> Fixes [YOCTO #3589].
>
> Signed-off-by: Tom Zanussi<tom.zanussi@intel.com>
> ---
> meta/classes/module.bbclass | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/meta/classes/module.bbclass b/meta/classes/module.bbclass
> index e8d32eb..ebb0880 100644
> --- a/meta/classes/module.bbclass
> +++ b/meta/classes/module.bbclass
> @@ -3,7 +3,7 @@ DEPENDS += "virtual/kernel"
>
> inherit module-base
>
> -addtask make_scripts before do_compile
> +addtask make_scripts after do_patch before do_compile
> do_make_scripts[lockfiles] = "${TMPDIR}/kernel-scripts.lock"
> do_make_scripts[deptask] = "do_populate_sysroot"
>
prev parent reply other threads:[~2012-12-14 8:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 5:27 [PATCH 0/1] Fix for build lttng-modules build error tom.zanussi
2012-12-14 5:27 ` [PATCH 1/1] module.bbclass: make sure do_make_scripts() executes after do_patch() tom.zanussi
2012-12-14 5:31 ` Bruce Ashfield [this message]
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=50CAB9A8.7010101@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=tom.zanussi@intel.com \
/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