Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Matthew McClintock <msm-oss@mcclintock.net>
Subject: Re: [PATCH v2] u-boot: add workaround patch for missing python dev
Date: Fri, 07 Jul 2017 11:47:12 +0100	[thread overview]
Message-ID: <1499424432.30311.1.camel@linuxfoundation.org> (raw)
In-Reply-To: <20170706182313.18992-1-msm-oss@mcclintock.net>

On Thu, 2017-07-06 at 13:23 -0500, Matthew McClintock wrote:
> Per the comments in the included patch:
> 
> tools: disable _libfdt.so (swig present, python-dev missing breakage)
> 
>  This is probing for tools and enabling if swig is found, however Python
>  libraries might be absent per the comment. This is just a host tool so
>  let's just disable it entirely for the now.

Can we ever find this given swig isn't in HOSTTOOLS with RSS? Do we
just need this on pre-pyro?

I don't really want to carry an non-upstreamable patch if we don't need
it.

Cheers,

Richard


      parent reply	other threads:[~2017-07-07 10:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-06 18:23 [PATCH v2] u-boot: add workaround patch for missing python dev Matthew McClintock
2017-07-07 10:12 ` Burton, Ross
2017-07-07 10:47 ` 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=1499424432.30311.1.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=msm-oss@mcclintock.net \
    /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