Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Burton, Ross" <ross.burton@intel.com>,
	Hongxu Jia <hongxu.jia@windriver.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] python3: fix do_configure check platform triplet error
Date: Fri, 11 Mar 2016 09:08:49 +0000	[thread overview]
Message-ID: <1457687329.2804.250.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAJTo0LZGEEq3LQV-83A1vJE7hfVwsPWOmXk1nX1E7G0JiskSPA@mail.gmail.com>

On Fri, 2016-03-11 at 09:04 +0000, Burton, Ross wrote:
> 
> On 11 March 2016 at 07:40, Hongxu Jia <hongxu.jia@windriver.com>
> wrote:
> > For p1022ds bsp, the MULTIARCH is powerpc-linux-gnuspev1 and
> > python3 did not recognize the extra 'v1' which caused python3
> > configure error for the platform triplet.
> > 
> Forgive me for dry-by commenting without a lot of clue about this,
> but doesn't that suggest instead that the C function to emit the
> triplets is in fact wrong?

Following the links does give more context. The "bad" triplet is
actually coming from gcc and Hongxu's original patch did change gcc to
"fix" it. Unfortunately it does so at the risk of other problems to
gcc.

The gcc-cross recipes aren't working entirely correctly at the moment
and its just good luck (and sstate) which are meaning things do
actually work out.

The trouble is that changing gcc right now to fix this properly isn't
something we can easily do. So this patch might be the right short term
workaround.

Cheers,

Richard


      reply	other threads:[~2016-03-11  9:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-11  7:40 [PATCH V2 0/1] fix python3 do_configure failed on meta-fsl-ppc with MACHINE = "p1022ds" Hongxu Jia
2016-03-11  7:40 ` [PATCH 1/1] python3: fix do_configure check platform triplet error Hongxu Jia
2016-03-11  9:04   ` Burton, Ross
2016-03-11  9:08     ` Richard Purdie [this message]

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=1457687329.2804.250.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox