From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] uboot-tools: disable libfdt swig wrapper
Date: Thu, 4 May 2017 17:12:48 +0200 [thread overview]
Message-ID: <20170504171248.77c9f3ff@free-electrons.com> (raw)
In-Reply-To: <1493697677-24802-1-git-send-email-matthew.weber@rockwellcollins.com>
Hello,
On Mon, 1 May 2017 23:01:17 -0500, Matt Weber wrote:
> The current tools build assumes the host system
> when trying to detect if swig/python are present.
> It then uses those tools from the path.
>
> The upstream RFC included this commit set's patch
> but offered up discussion on how to cleanly
> introduce a better method for detecting swig and
> using the tools. The tools build really needs to
> be sysroot and prefix/host dir tools aware.
>
> Upsteam submission for RFC:
> https://lists.denx.de/pipermail/u-boot/2017-May/289520.html
>
> Workaround for:
> http://autobuild.buildroot.net/results/6d5/6d52ac8bb71012aea6fc4c679691b31a3366728b
>
> Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com>
> ---
> ...nditionally-disable-python-libfdt-wrapper.patch | 44 ++++++++++++++++++++++
> package/uboot-tools/uboot-tools.mk | 5 +++
> 2 files changed, 49 insertions(+)
> create mode 100644 package/uboot-tools/0005-tools-conditionally-disable-python-libfdt-wrapper.patch
As I said, I'm not entirely happy with this solution, but it does the
job for now, and nobody has provided a different patch.
So: applied, thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-05-04 15:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 4:01 [Buildroot] [PATCH 1/1] uboot-tools: disable libfdt swig wrapper Matt Weber
2017-05-04 15:12 ` Thomas Petazzoni [this message]
2017-07-13 5:49 ` Jörg Krause
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=20170504171248.77c9f3ff@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.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 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.