From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14911] New: host-python3 build needs python3 on the host
Date: Tue, 12 Jul 2022 12:55:30 +0000 [thread overview]
Message-ID: <bug-14911-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=14911
Bug ID: 14911
Summary: host-python3 build needs python3 on the host
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: thomas.petazzoni@bootlin.com
CC: buildroot@uclibc.org
Target Milestone: ---
Since commit 9c0c7846cdb63f3ed62563c4f532ad02ad0a1c98 ("support/dependencies:
don't check for python on the host"), we no longer require to have Python
installed on the host system. However, on a minimal Ubuntu container, without
python3 available, the build of host-python3 fails with:
python3 ./Tools/scripts/update_file.py ./Python/importlib_external.h
./Python/importlib_external.h.new
make[2]: python3: Command not found
make[2]: *** [Makefile:754: regen-importlib] Error 127
make[1]: *** [package/pkg-generic.mk:292:
/output/build/host-python3-3.10.4/.stamp_built] Error 2
make: *** [Makefile:23: _all] Error 2
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2022-07-12 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 12:55 bugzilla [this message]
2022-07-27 13:32 ` [Buildroot] [Bug 14911] host-python3 build needs python3 on the host bugzilla
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-14911-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/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