All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mei Lei <lei.mei@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1]python-native: Fix a compiler finding issue
Date: Thu, 28 Jul 2011 15:20:35 +0800	[thread overview]
Message-ID: <cover.1311836896.git.lei.mei@intel.com> (raw)

Hi,
    This patch will fix an compiler finding issue.
    The CC variable, its value sometimes like "x86_64-poky-linux-gcc   -m64 --sysroot=/${TMPDIR}/sysroots/qemux86-64", contains option information. This will confuse python when finding the compiler name, wrong compiler name "qemux86-64" were found rather than the "x86_64-poky-linux-gcc".
    When I fixing python-pycairo multilib dir issue, above issue appeared and block the compile process. Please review it.

Thanks
Lei

The following changes since commit 819f18f8bc000f13b644edc194d2a12b4ea5fecf:
  Richard Purdie (1):
        Move architecture specific TARGET_OS mangling into tune files

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib lmei3/python-pycairo
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=lmei3/python-pycairo

Mei Lei (1):
  python-native: Fix a compiler finding issue

 .../python/python-native/unixccompiler.patch       |   20 ++++++++++++++++++++
 .../recipes-devtools/python/python-native_2.6.6.bb |    3 ++-
 2 files changed, 22 insertions(+), 1 deletions(-)
 create mode 100644 meta/recipes-devtools/python/python-native/unixccompiler.patch




             reply	other threads:[~2011-07-28  7:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-28  7:20 Mei Lei [this message]
2011-07-28  7:20 ` [PATCH 1/1] python-native: Fix a compiler finding issue Mei Lei
2011-07-28 15:08   ` Tom Rini
2011-07-29  1:15     ` Mei, Lei
2011-07-29  1:43       ` Tom Rini
2011-07-29  6:58         ` Mei, Lei
2011-07-29 15:28           ` Tom Rini
2011-08-01 12:41             ` Mei, Lei
2011-08-01 17:27               ` Khem Raj
2011-08-02  3:08                 ` Mei, Lei
2011-08-10 23:28 ` [PATCH 0/1]python-native: " Saul Wold

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=cover.1311836896.git.lei.mei@intel.com \
    --to=lei.mei@intel.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 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.