From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Chen Qi <Qi.Chen@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] toolchain-script: use immediate expansion for TOOLCHAIN_CONFIGSITE_NOCACHE
Date: Fri, 23 Sep 2016 15:37:55 +0100 [thread overview]
Message-ID: <1474641475.7207.370.camel@linuxfoundation.org> (raw)
In-Reply-To: <b837a1b7714ef69601f5a12cbf5baf925dfb1a7b.1474619360.git.Qi.Chen@windriver.com>
On Fri, 2016-09-23 at 16:30 +0800, Chen Qi wrote:
> Use immediate expansion for the assignment to avoid other classes
> modifying
> variables like HOST_ARCH which changes the result. This happens in
> the
> meta-environment recipe. It inherits cross-canadian which changes
> HOST_ARCH
> from TARGET_ARCH to SDK_ARCH, resulting in wrong site config files in
> the
> generated SDK.
>
> [YOCTO #10255]
>
> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
> ---
> meta/classes/toolchain-scripts.bbclass | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
I've not merged this as yet since I worry that this is something we'd
easily break again. It all depends which order classes are included and
moving the cross-canadian inherit in meta-environment would break this
even with immediate expansion.
I think the best way to fix this might be to change the meta-
environment to add:
# Need to expand here before cross-candian changes HOST_ARCH -> SDK_ARCH
TOOLCHAIN_CONFIGSITE_NOCACHE := "${TOOLCHAIN_CONFIGSITE_NOCACHE}"
before it inherits cross-candian, then the problem is explicitly
recorded and worked around.
Cheers,
Richard
next prev parent reply other threads:[~2016-09-23 14:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 8:30 [PATCH 0/1] toolchain-script: use immediate expansion for TOOLCHAIN_CONFIGSITE_NOCACHE Chen Qi
2016-09-23 8:30 ` [PATCH 1/1] " Chen Qi
2016-09-23 14:37 ` Richard Purdie [this message]
2016-09-26 3:20 ` ChenQi
-- strict thread matches above, loose matches on Subject: below --
2015-10-30 7:50 [PATCH 0/1] " Chen Qi
2015-10-30 7:50 ` [PATCH 1/1] " Chen Qi
2016-03-15 6:53 ` ChenQi
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=1474641475.7207.370.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Qi.Chen@windriver.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