9000889da7
Qemu uses the host-python when building, but the .mk file is pointing the host-python interpreter to the target python site-packages, which is both incorrect and also unneeded. Qemu doesn't need any extra packages [1], so there's no need to provide this path. And indeed qemu builds fine when setting the path to a non-existent directory. Since target qemu neither depends on nor selects target python, it's quite possible to build qemu without a target python, in which case the supplied PYTHONPATH is a non-existent directory. But even if qemu did want a python package, pointing the host-python to the target site-packages will not work. The package could contain a compiled shared library for the target architecture that the host python can not load. This can be tested by adding "import numpy" to one of qemu's python scripts and observing target python-numpy failing to load when the script is run at build time. [1] https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg01758.html "Avoid third-party package dependencies - QEMU currently has none!" Signed-off-by: Trent Piepho <tpiepho@impinj.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> |
||
|---|---|---|
| arch | ||
| board | ||
| boot | ||
| configs | ||
| docs | ||
| fs | ||
| linux | ||
| package | ||
| support | ||
| system | ||
| toolchain | ||
| utils | ||
| .defconfig | ||
| .flake8 | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .gitlab-ci.yml.in | ||
| CHANGES | ||
| Config.in | ||
| Config.in.legacy | ||
| COPYING | ||
| DEVELOPERS | ||
| Makefile | ||
| Makefile.legacy | ||
| README | ||
Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation. The documentation can be found in docs/manual. You can generate a text document with 'make manual-text' and read output/docs/manual/manual.text. Online documentation can be found at http://buildroot.org/docs.html To build and use the buildroot stuff, do the following: 1) run 'make menuconfig' 2) select the target architecture and the packages you wish to compile 3) run 'make' 4) wait while it compiles 5) find the kernel, bootloader, root filesystem, etc. in output/images You do not need to be root to build or run buildroot. Have fun! Buildroot comes with a basic configuration for a number of boards. Run 'make list-defconfigs' to view the list of provided configurations. Please feed suggestions, bug reports, insults, and bribes back to the buildroot mailing list: buildroot@buildroot.org You can also find us on #buildroot on Freenode IRC. If you would like to contribute patches, please read https://buildroot.org/manual.html#submitting-patches