From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] qt4: move functions from python to shell style
Date: Tue, 08 May 2012 14:05:07 +0100 [thread overview]
Message-ID: <1336482307.25084.77.camel@ted> (raw)
In-Reply-To: <ad81aeddba7ac9bbd855e92304dafab2a811b523.1336454749.git.dongxiao.xu@intel.com>
On Tue, 2012-05-08 at 13:28 +0800, Dongxiao Xu wrote:
> In qt4's do_configure operation, it will refer to some variables that
> are derived from 'd', however these variable values may be not correct
> in multilib case since the extraction of these variables happens before
> the multilib handler.
>
> The fix is to move these python style functions back to shell style.
>
> This fixes [YOCTO #2355]
>
> Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
> ---
> meta/recipes-qt/qt4/qt4-embedded.inc | 2 +-
> meta/recipes-qt/qt4/qt4-tools-nativesdk.inc | 5 ++-
> meta/recipes-qt/qt4/qt4-x11-free.inc | 2 +-
> meta/recipes-qt/qt4/qt4.inc | 5 ++-
> meta/recipes-qt/qt4/qt4_arch.inc | 36 ++++++++++++---------------
> 5 files changed, 24 insertions(+), 26 deletions(-)
Merged to master with a fix to some of the whitespace, thanks.
Richard
next prev parent reply other threads:[~2012-05-08 13:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 5:28 [PATCH 0/1 v3][PULL] Fix bug 2355 Dongxiao Xu
2012-05-08 5:28 ` [PATCH 1/1] qt4: move functions from python to shell style Dongxiao Xu
2012-05-08 13:05 ` Richard Purdie [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-23 8:53 [PATCH 0/1 v2][PULL] Fix bug 2355 Dongxiao Xu
2012-04-23 8:53 ` [PATCH 1/1] qt4: move functions from python to shell style Dongxiao Xu
2012-04-24 10:50 ` Paul Eggleton
2012-05-08 5:34 ` Xu, Dongxiao
2012-04-21 15:05 [PATCH 0/1][PULL] Fix bug 2355 Dongxiao Xu
2012-04-21 15:05 ` [PATCH 1/1] qt4: move functions from python to shell style Dongxiao Xu
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=1336482307.25084.77.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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