All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Agner <stefan@agner.ch>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] libfdt: fix build with Python 3
Date: Wed, 29 Mar 2017 12:41:23 -0700	[thread overview]
Message-ID: <20170329194123.2361-1-stefan@agner.ch> (raw)

From: Stefan Agner <stefan.agner@toradex.com>

For some reason Python 3 seems to think it does not need to build
the library. Using the --force parameter makes sure that the library
gets built always. This is especially important since we move the
library in the next step of the Makefile, hence forcing a rebuild
every time the higher level Makefile triggers a rebuild is required
to make sure the library is always there.

Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
---

 lib/libfdt/setup.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/libfdt/setup.py b/lib/libfdt/setup.py
index 62e7bcc1ac..845a0c2b10 100644
--- a/lib/libfdt/setup.py
+++ b/lib/libfdt/setup.py
@@ -27,7 +27,7 @@ libfdt_module = Extension(
     extra_compile_args =  cflags
 )
 
-sys.argv = [progname, '--quiet', 'build_ext', '--inplace']
+sys.argv = [progname, '--quiet', 'build_ext', '--inplace', '--force']
 
 setup (name = 'libfdt',
        version = '0.1',
-- 
2.12.1

             reply	other threads:[~2017-03-29 19:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-29 19:41 Stefan Agner [this message]
2017-04-01  4:23 ` [U-Boot] [PATCH] libfdt: fix build with Python 3 Simon Glass
2017-04-05 18:08   ` Stefan Agner
2017-04-05 18:11     ` Simon Glass
2017-04-10 20:52       ` Simon Glass
2017-06-25 21:59         ` Stephen Arnold
2017-04-03 10:30 ` Stefano Babic
2017-04-03 16:41   ` Stefan Agner
2017-04-03 17:35     ` Stefano Babic
2017-04-03 21:02       ` Stefan Agner
2017-04-04  8:53         ` Stefano Babic
2017-04-04 18:44           ` Stefan Agner
2017-04-05 17:26             ` Stefano Babic
2017-04-05 18:05               ` Stefan Agner

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=20170329194123.2361-1-stefan@agner.ch \
    --to=stefan@agner.ch \
    --cc=u-boot@lists.denx.de \
    /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.