From: Phil Blundell <pb@pbcl.net>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] allarch.bbclass: Set FEED_ARCH to 'allarch'
Date: Tue, 14 Jun 2011 10:40:31 +0100 [thread overview]
Message-ID: <1308044431.25285.237.camel@phil-desktop> (raw)
In-Reply-To: <1308029130-29774-1-git-send-email-raj.khem@gmail.com>
On Mon, 2011-06-13 at 22:25 -0700, Khem Raj wrote:
> PACKAGE_ARCH is set to BASE_PACKAGE_ARCH so we do not
> need to define it here since we already define BASE_PACKAGE_ARCH
>
> Additionally set FEED_ARCH to 'allarch' some distros e.g.
> angstrom sets FEED_ARCH like
>
> FEED_ARCH ?= "${BASE_PACKAGE_ARCH}"
Um? Surely if FEED_ARCH is defined in terms of B_P_A then just setting
the latter variable ought to be enough. Why do you need to set both?
> and 'all' doesnt go well for FEED_ARCH as it ends up with
> parsing error for x86 machines.
That sounds a bit odd as well. I wouldn't have expected any value of
FEED_ARCH to result in parsing errors. What actually goes wrong?
p.
>
> This might be a latent bug in bitbake but allarch.bbclass
> excavated it and we burry it in the same class.
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> meta/classes/allarch.bbclass | 5 ++---
> 1 files changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/meta/classes/allarch.bbclass b/meta/classes/allarch.bbclass
> index e3ac392..971cb92 100644
> --- a/meta/classes/allarch.bbclass
> +++ b/meta/classes/allarch.bbclass
> @@ -2,9 +2,8 @@
> # This class is used for architecture independent recipes/data files (usally scripts)
> #
>
> -BASE_PACKAGE_ARCH = "all"
> -PACKAGE_ARCH = "all"
> -
> +BASE_PACKAGE_ARCH = "allarch"
> +FEED_ARCH = "allarch"
> # No need for virtual/libc or a cross compiler
> INHIBIT_DEFAULT_DEPS = "1"
>
prev parent reply other threads:[~2011-06-14 9:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 5:25 [PATCH] allarch.bbclass: Set FEED_ARCH to 'allarch' Khem Raj
2011-06-14 7:43 ` Koen Kooi
2011-06-14 9:40 ` Phil Blundell [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=1308044431.25285.237.camel@phil-desktop \
--to=pb@pbcl.net \
--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