All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] uboot-tools: bugfix libfdt python build
Date: Tue, 17 Oct 2017 20:54:37 +0200	[thread overview]
Message-ID: <20171017205437.4689e5f0@windsurf.lan> (raw)
In-Reply-To: <CANQCQpZFwWLqMZ1Y6mCWQieVFgka+uZs_vJeS6+BPOLUhyPF0A@mail.gmail.com>

Hello,

On Tue, 17 Oct 2017 13:16:01 -0500, Matthew Weber wrote:

> Looking at the current development on uboot upstream, the 2017.11
> release will be the bump we should take.  With that they cleaned up
> the tools having some default python/swig dependencies by having
> libfdt enabled in uboot kconfig.  We'll still have to update the
> BR2_TARGET_UBOOT_NEEDS_PYLIBFDT option in the uboot package so that it
> includes providing the PYTHON path variable to the build.  The
> upstream changes also removed the need for this patchset against
> uboot-tools fixing python and swig patch issues.

Thanks for looking into this!

> I'll send a proposed patchset for a 2017.11 bump later this month
> after testing with a -rc

Do we have a workaround in the mean time, to avoid trashing the
autobuilder results?

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-10-17 18:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-13  2:35 [Buildroot] [PATCH] uboot-tools: bugfix libfdt python build Matt Weber
2017-10-13 14:11 ` Thomas Petazzoni
2017-10-14  1:01   ` Matthew Weber
2017-10-14 21:44     ` Matthew Weber
2017-10-15 12:09       ` Fabio Estevam
2017-10-17 18:16         ` Matthew Weber
2017-10-17 18:54           ` Thomas Petazzoni [this message]
2017-10-17 19:00             ` Matthew Weber
2017-10-17 19:03               ` Fabio Estevam
2017-10-17 20:14                 ` Matthew Weber

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=20171017205437.4689e5f0@windsurf.lan \
    --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.