Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] Multilib build fixes
Date: Thu, 19 Jul 2012 21:05:42 -0700	[thread overview]
Message-ID: <5008D916.60008@linux.intel.com> (raw)
In-Reply-To: <1342699213-435-1-git-send-email-bogdan.a.marinescu@intel.com>

On 07/19/2012 05:00 AM, Bogdan Marinescu wrote:
> 1. STAGING_KERNEL_DIR was getting an invalid MLPREFIX. Fix this by forcing the expansion in multilib.conf.
> 2. Added multilib rule for 'perf'.
> ---
>   meta/conf/multilib.conf |    2 ++
>   1 file changed, 2 insertions(+)
>
> diff --git a/meta/conf/multilib.conf b/meta/conf/multilib.conf
> index bb21815..6a89a53 100644
> --- a/meta/conf/multilib.conf
> +++ b/meta/conf/multilib.conf
> @@ -6,6 +6,7 @@ MULTILIB_SAVE_VARNAME = "DEFAULTTUNE"
>
>   MULTILIBS ??= "multilib:lib32"
>
> +STAGING_KERNEL_DIR := "${STAGING_KERNEL_DIR}"
>   STAGING_DIR_HOST = "${STAGING_DIR}/${MLPREFIX}${MACHINE}"
>   STAGING_DIR_TARGET = "${STAGING_DIR}/${MLPREFIX}${MACHINE}"
>
> @@ -512,6 +513,7 @@ BBCLASSEXTEND_append_pn-pax-utils = " ${MULTILIBS}"
>   BBCLASSEXTEND_append_pn-pciutils = " ${MULTILIBS}"
>   BBCLASSEXTEND_append_pn-pcmanfm = " ${MULTILIBS}"
>   BBCLASSEXTEND_append_pn-pcmciautils = " ${MULTILIBS}"
> +BBCLASSEXTEND_append_pn-perf = " ${MULTILIBS}"
>   BBCLASSEXTEND_append_pn-perl = " ${MULTILIBS}"
>   BBCLASSEXTEND_append_pn-pixman = " ${MULTILIBS}"
>   BBCLASSEXTEND_append_pn-pkgconfig = " ${MULTILIBS}"
>
Merged into OE-Core

Thanks
	Sau!




      reply	other threads:[~2012-07-20  4:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-19 12:00 [PATCH] Multilib build fixes Bogdan Marinescu
2012-07-20  4:05 ` Saul Wold [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=5008D916.60008@linux.intel.com \
    --to=sgw@linux.intel.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