From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] python3 support for pylibfdt
Date: Wed, 19 Jun 2019 14:22:19 -0400 [thread overview]
Message-ID: <20190619182219.GT9388@bill-the-cat> (raw)
In-Reply-To: <CALeDE9O6yF6TiLG24V4GHK4T6=c-Ci_Bp0PehH6wBatZeKOGnQ@mail.gmail.com>
On Tue, Jun 18, 2019 at 10:39:54AM +0100, Peter Robinson wrote:
> Hi Simon,
>
> With the EOL of python2 soon I've been looking at the Fedora U-Boot
> builds to see what it would take to move over to python3. There's a
> couple of issues building the bundled pylibfdt, the first is the
> Makefile hard codes python2, the second is that the generated
> libfdt_wrap.c doesn't seem to find the python3 version of Python.h
> (errors below).
>
> It seems upstream now supports building pylibfdt with dtc 1.5.0 but I
> couldn't quite work out how this fits into the U-Boot bundled version.
> Is there plans to be able to support pylibfdt with python3?
Sounds like we need to run the normal kernel script to re-sync with
upstream? Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190619/159dac6e/attachment.sig>
next prev parent reply other threads:[~2019-06-19 18:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 9:39 [U-Boot] python3 support for pylibfdt Peter Robinson
2019-06-19 18:22 ` Tom Rini [this message]
2019-06-20 10:45 ` Peter Robinson
2019-06-26 21:32 ` Tom Rini
2019-06-28 12:38 ` Peter Robinson
2019-06-28 12:51 ` Tom Rini
2019-06-28 13:52 ` Simon Glass
2019-07-24 9:23 ` Peter Robinson
2019-07-24 14:47 ` Simon Glass
2019-08-28 11:46 ` Peter Robinson
2019-08-28 13:44 ` Simon Glass
2019-08-28 13:47 ` Tom Rini
2019-08-28 16:11 ` Simon Glass
2019-08-29 1:19 ` Tom Rini
2019-09-04 14:36 ` Simon Glass
2019-10-25 3:31 ` Simon Glass
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=20190619182219.GT9388@bill-the-cat \
--to=trini@konsulko.com \
--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.