From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] sane-toolchain.inc: FEED_ARCH should be prepended to OVERRIDES
Date: Wed, 22 Dec 2010 09:32:58 +0100 [thread overview]
Message-ID: <iesd3q$kf4$1@dough.gmane.org> (raw)
In-Reply-To: <1292999142-28338-1-git-send-email-raj.khem@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 22-12-10 07:25, Khem Raj wrote:
> Currently it ends up after local override and hence appears first in FILESPATH
> and for buiding uclibc_git.bb on qemuarm it picks wrong uClibc.machine file from
> uclibc-git/armv5te where as it should have picked from uclibc-git/qemuarm
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> conf/distro/include/sane-toolchain.inc | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/conf/distro/include/sane-toolchain.inc b/conf/distro/include/sane-toolchain.inc
> index 6802eb2..f5ca22b 100644
> --- a/conf/distro/include/sane-toolchain.inc
> +++ b/conf/distro/include/sane-toolchain.inc
> @@ -75,7 +75,7 @@ require conf/distro/include/toolchain-${TOOLCHAIN_TYPE}.inc
> # Add FEED_ARCH to the overrides list so that we can override the
> # ARM_INSTRUCTION_SET like below
>
> -OVERRIDES .= ":${FEED_ARCH}"
> +OVERRIDES =. "${FEED_ARCH}:"
>
> # ARM920T and up can use thumb mode to decrease binary size at the expense of speed
> # (the complete story is a bit more nuanced due to cache starvation)
Shouldn't that be BASE_PACKAGE_ARCH nowadays?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFNEbe6MkyGM64RGpERAnMHAJ9x+kBJeouJPeVMJxQlgWNzTK05sACfSFur
ckz3MaEHqpx3h9rPdo9pKn8=
=xnMX
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-12-22 8:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 6:25 [PATCH] sane-toolchain.inc: FEED_ARCH should be prepended to OVERRIDES Khem Raj
2010-12-22 8:32 ` Koen Kooi [this message]
2010-12-22 18:03 ` Khem Raj
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='iesd3q$kf4$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@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