All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] boot/uboot: fix build for sunxi targets
Date: Mon, 16 Jan 2017 21:04:27 +0100	[thread overview]
Message-ID: <1484597067.8221.1.camel@embedded.rocks> (raw)
In-Reply-To: <874m13c7uv.fsf@dell.be.48ers.dk>

Hi Peter,

On Fri, 2017-01-13 at 16:11 +0100, Peter Korsgaard wrote:
> > > > > > "J?rg" == J?rg Krause <joerg.krause@embedded.rocks> writes:
> 
> ?> Since version 2017.01 U-Boot needs to run the binman tool on the
> host machine
> ?> for building the 'u-boot-sunxi-with-spl.bin' target. The binman
> tool is written
> ?> in Python 2 so we need to add the python host package when
> building this
> ?> target, otherwise the build fails:
> 
> ?> ```
> ?>???BINMAN??u-boot-sunxi-with-spl.bin
> ?>???File "./tools/binman/binman", line 49
> ?>?????print result
> ?>????????????????^
> ?> SyntaxError: Missing parentheses in call to 'print'
> ?> make[1]: *** [Makefile:1090: u-boot-sunxi-with-spl.bin] Error 1
> ?> ```
> 
> ?> Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
> 
> That's not very nice :/
> 
> We already check for python on the build machine in dependencies.sh,
> so
> perhaps we could patch the binman sources to be compatible with
> python
> 3 (and send the patch upstream)?
> 
> Is that something you could look into?

I would rather not do the porting, but I can ask upstream about
supporting Python 3.

J?rg

      reply	other threads:[~2017-01-16 20:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-13  0:04 [Buildroot] [PATCH] boot/uboot: fix build for sunxi targets Jörg Krause
2017-01-13 15:11 ` Peter Korsgaard
2017-01-16 20:04   ` Jörg Krause [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=1484597067.8221.1.camel@embedded.rocks \
    --to=joerg.krause@embedded.rocks \
    --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.