Openembedded Core Discussions
 help / color / mirror / Atom feed
From: richard.purdie@linuxfoundation.org
To: Ming Liu <liu.ming50@gmail.com>,
	OE-core <openembedded-core@lists.openembedded.org>
Cc: Cheuk Wing Leung <cwleung@kth.se>
Subject: Re: [PATCH] python3: set PYTHONHOME for nativesdk
Date: Fri, 12 Oct 2018 15:00:11 +0100	[thread overview]
Message-ID: <a5b826c08416843fd31d1668524a1269ed3d6682.camel@linuxfoundation.org> (raw)
In-Reply-To: <CALatG=4wF+yKGxkV5EmxBHdPvMr4FMQJpip01f1F6YH=5f6hbA@mail.gmail.com>

On Fri, 2018-10-12 at 13:37 +0200, Ming Liu wrote:
> Hi, Richard:
> 
> > I think its this which is causing breakage:
> >
> > 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/20/builds/106/steps/7/logs/step3b
> >
> > 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/20/builds/106/steps/7/logs/step2b
> >
> > 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/20/builds/106/steps/7/logs/step1b
> 
> Are you sure about this? This patch creates a nativesdk python3
> wrapper which supposes to run on SDK machine, it should not impact
> native sysroot binaries, and I could not reproduce the error with the
> patch applied on my local machine. (Ubuntu-16.04)

Sorry for the false alarm, its actually the cmake patches sine after
dropping those, -next built cleanly. Cc'ing Pascal Bach...

Cheers,

Richard



      reply	other threads:[~2018-10-12 14:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-11 14:15 [PATCH] python3: set PYTHONHOME for nativesdk liu.ming50
2018-10-11 22:43 ` Richard Purdie
2018-10-12 11:37 ` Ming Liu
2018-10-12 14:00   ` 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=a5b826c08416843fd31d1668524a1269ed3d6682.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=cwleung@kth.se \
    --cc=liu.ming50@gmail.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