From: Hongxu Jia <hongxu.jia@windriver.com>
To: <openembedded-core@lists.openembedded.org>, <ross.burton@intel.com>
Subject: Re: [PATCH 1/1] multilib.bbclass/package_manager.py: fix <multilib>-meta-toolchain build failure
Date: Wed, 15 Oct 2014 15:53:52 +0800 [thread overview]
Message-ID: <543E2810.3040102@windriver.com> (raw)
In-Reply-To: <19a9c5389b842d65e4d0e3a5068d9404bb5324ac.1413352525.git.hongxu.jia@windriver.com>
On 10/15/2014 01:59 PM, Hongxu Jia wrote:
> @@ -61,7 +61,7 @@ class RpmIndexer(Indexer):
> eext = ext.split(':')
> if len(eext) > 1 and eext[0] == 'multilib':
> localdata = bb.data.createCopy(self.d)
> - default_tune_key = "DEFAULTTUNE_virtclass-multilib-" + eext[1]
> + default_tune_key = "DEFAULTTUNE_ML_" + eext[1]
> default_tune = localdata.getVar(default_tune_key, False)
> if default_tune:
> localdata.setVar("DEFAULTTUNE", default_tune)
It caused build failure of meta-toolchain, in order to avoid it, we
should use DEFAULTTUNE_virtclass-multilib-lib32 first, if it is not
available, and try to use DEFAULTTUNE_ML_<multilib>
So it does not affect previous build workflow.
Please drop it, V2 incoming
//Hongxu
next prev parent reply other threads:[~2014-10-15 7:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 5:58 [PATCH 0/1] multilib.bbclass/package_manager.py: fix <multilib>-meta-toolchain build failure Hongxu Jia
2014-10-15 5:59 ` [PATCH 1/1] " Hongxu Jia
2014-10-15 7:53 ` Hongxu Jia [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-10-15 9:23 [PATCH V2 0/1] " Hongxu Jia
2014-10-15 9:23 ` [PATCH 1/1] " Hongxu Jia
2014-10-15 11:00 ` Laurentiu Palcu
2014-10-15 11:32 ` Hongxu Jia
2014-10-15 12:31 [PATCH V3 0/1] " Hongxu Jia
2014-10-15 12:31 ` [PATCH 1/1] " Hongxu Jia
2014-10-15 13:27 ` Laurentiu Palcu
2014-10-15 13:57 ` Hongxu Jia
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=543E2810.3040102@windriver.com \
--to=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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.