From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] linux-tools: multilib compilation fix
Date: Thu, 21 Jun 2012 13:29:49 +0100 [thread overview]
Message-ID: <1340281789.1640.106.camel@ted> (raw)
In-Reply-To: <1340180732-26710-1-git-send-email-bogdan.a.marinescu@intel.com>
On Wed, 2012-06-20 at 11:25 +0300, Bogdan Marinescu wrote:
> This patch makes linux-tools compile properly on multilib configurations
> (which failed because of some invalid dependencies). Tested by compiling
> lib32-core-image-sato-sdk.
>
> Signed-off-by: Bogdan Marinescu <bogdan.a.marinescu@intel.com>
> ---
> meta/recipes-kernel/linux/linux-tools.inc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-kernel/linux/linux-tools.inc b/meta/recipes-kernel/linux/linux-tools.inc
> index 3b03c05..048608c 100644
> --- a/meta/recipes-kernel/linux/linux-tools.inc
> +++ b/meta/recipes-kernel/linux/linux-tools.inc
> @@ -34,7 +34,7 @@ do_install_perf[umask] = "022"
>
> PERFDEPENDS = "virtual/${MLPREFIX}libc:do_populate_sysroot ${MLPREFIX}elfutils:do_populate_sysroot ${MLPREFIX}binutils:do_populate_sysroot"
> PERFDEPENDS_libc-uclibc = ""
> -PERFRDEPENDS = "python perl elfutils"
> +PERFRDEPENDS = "${MLPREFIX}python ${MLPREFIX}perl ${MLPREFIX}elfutils"
> PERFRDEPENDS_libc-uclibc = ""
>
> do_compile_perf[depends] = "${PERFDEPENDS}"
Bruce has just totally rearranged this code. Could you check if the new
recipe still suffers from this issue please?
Cheers,
Richard
next prev parent reply other threads:[~2012-06-21 12:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 8:25 [PATCH] linux-tools: multilib compilation fix Bogdan Marinescu
2012-06-21 12:29 ` Richard Purdie [this message]
2012-06-21 12:32 ` Marinescu, Bogdan A
2012-06-21 12:33 ` Bruce Ashfield
2012-06-21 12:39 ` Richard Purdie
2012-06-21 12:42 ` Bruce Ashfield
2012-06-21 14:59 ` Marinescu, Bogdan A
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=1340281789.1640.106.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.