From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11706] binman (U-boot tool) cannot find libfdt "binman: No module named _libfdt" if python3 selected
Date: Thu, 15 Aug 2019 14:03:46 +0000 [thread overview]
Message-ID: <bug-11706-163-2fxe19rZRF@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11706-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11706
--- Comment #2 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
I can indeed reproduce the issue with the following defconfig:
BR2_arm=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_TOOLCHAIN_EXTERNAL_CUSTOM=y
BR2_TOOLCHAIN_EXTERNAL_DOWNLOAD=y
BR2_TOOLCHAIN_EXTERNAL_URL="http://autobuild.buildroot.org/toolchains/tarballs/br-arm-full-2019.05.1.tar.bz2"
BR2_TOOLCHAIN_EXTERNAL_GCC_4_9=y
BR2_TOOLCHAIN_EXTERNAL_HEADERS_4_14=y
BR2_TOOLCHAIN_EXTERNAL_LOCALE=y
# BR2_TOOLCHAIN_EXTERNAL_HAS_THREADS_DEBUG is not set
BR2_TOOLCHAIN_EXTERNAL_CXX=y
BR2_INIT_NONE=y
BR2_SYSTEM_BIN_SH_NONE=y
# BR2_PACKAGE_BUSYBOX is not set
BR2_PACKAGE_LIBVIPS=y
# BR2_TARGET_ROOTFS_TAR is not set
The problem is that binman has the following shebang:
#!/usr/bin/env python2
When python3 is selected for the target, we build host-python3, and we install
all host-Python modules for host-python3. So when binman uses python2, it uses
the system-provided python2, which does not have those additional Python
modules installed.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-08-15 14:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 8:07 [Buildroot] [Bug 11706] New: binman (U-boot tool) cannot find libfdt "binman: No module named _libfdt" if python3 selected bugzilla at busybox.net
2019-08-13 1:17 ` [Buildroot] [Bug 11706] " bugzilla at busybox.net
2019-08-15 14:03 ` bugzilla at busybox.net [this message]
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-2fxe19rZRF@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 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.