From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11706] New: binman (U-boot tool) cannot find libfdt "binman: No module named _libfdt" if python3 selected
Date: Wed, 27 Feb 2019 08:07:57 +0000 [thread overview]
Message-ID: <bug-11706-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=11706
Bug ID: 11706
Summary: binman (U-boot tool) cannot find libfdt "binman: No
module named _libfdt" if python3 selected
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: safyannikov at perco.ru
CC: buildroot at uclibc.org
Target Milestone: ---
U-Boot building fails with:
...
LD spl/u-boot-spl
OBJCOPY spl/u-boot-spl-nodtb.bin
COPY spl/u-boot-spl.bin
MKSUNXI spl/sunxi-spl.bin
BINMAN u-boot-sunxi-with-spl.bin
binman: No module named _libfdt
make[1]: *** [Makefile:1348: u-boot-sunxi-with-spl.bin] Error 1
This situation occurs on system with only python3 installed and after selecting
python3 to install on image
So far I can reproduce this situation by this way:
Take clean buildroot.
Configure it for for any sun7i-a20 board
Turn on U-boot and select creation of SPL
Turn on dtc and libfdt for uboot
Configure U-boot for sunxi boards
Build image.
And everything will be fine
After that cleanup, select python3, and try to build again
It does not make, and get error in this situation.
I remember there was a bug some years ago with uboot using python3 instead of
python2. That bug was fixed, but looks like 'binman' now stumble on the same
rope
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-02-27 8:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 8:07 bugzilla at busybox.net [this message]
2019-08-13 1:17 ` [Buildroot] [Bug 11706] binman (U-boot tool) cannot find libfdt "binman: No module named _libfdt" if python3 selected bugzilla at busybox.net
2019-08-15 14:03 ` bugzilla at busybox.net
2020-03-03 21:22 ` bugzilla at busybox.net
2020-05-29 21:04 ` bugzilla at busybox.net
2021-02-16 21:48 ` bugzilla at busybox.net
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=bug-11706-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox