68986ea301
systemd's configure is looking in $PATH to find utilities that will be needed at runtime. Usually, those utilties, when installed on the host, will be found in the same path they would be present on the target. For example, /usr/bin/mount on the host would also be /usr/bin/mount on the target, and all is find. Except when we need to install a host variant of util-linux, which will install mount in $(HOST_DIR), in which case systemd's configure would find that one. Of course, it is also very well possible that those utilities are not installed on the host in the same location they would be on the target, in case a user has manually installed some of those (e.g. in /usr/local/ or in /opt/) Forcibly set the path to those utilities, as they are expected to be on the target. For kexec, we can set it even though we do not depend on it (yet). systemd will appropriately test it at runtime. For quota, we point to non-existing files, so as to catch errors at runtime. It is to be noted that quotacheck is optional, while quotaon does not seem to be (a service file is always installed, that uses it). Note: utilties listed in the order they appear in configure.ac Reported-by: Adam Duskett <aduskett@gmail.com> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Maxime Hadjinlian <maxime.hadjinlian@gmail.com> Cc: Adam Duskett <aduskett@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> |
||
|---|---|---|
| arch | ||
| board | ||
| boot | ||
| configs | ||
| docs | ||
| fs | ||
| linux | ||
| package | ||
| support | ||
| system | ||
| toolchain | ||
| .defconfig | ||
| .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