e1550ef755
In the internal toolchain backend, we have a choice..endchoice block to allow the user to select the C library, between glibc, uClibc and musl. However, there are situations were no C library at all is supported. In this case, the choice does not appear, and does not allow to see the Config.in comments that are within the choice..endchoice block and that may explain why no C library is available. For example, on RISC-V 32-bit, the only C library supported is glibc, and the minimum kernel header version required by glibc on this architecture is 5.4.0. In a future commit, we are going to add this dependency on glibc (to fix build issues on configurations that have headers < 5.4.0). But since glibc is the only supported C library on RISC-V 32-bit, it means that the choice..endchoice for the C library contains no entry, preventing from seeing the Config.in comment. To address this issue, this commit adds a "dummy" BR2_TOOLCHAIN_BUILDROOT_NONE option that shows up in the choice..endchoice only when no C library is available. Thanks to this, the choice..endchoice is never empty, and the Config.in comments can be seen. If the user keeps BR2_TOOLCHAIN_BUILDROOT_NONE selected, then the build will anyway abort early because package/Makefile.in has a check to verify that a C library is selected, and aborts the build if not. Some could say that the problem should be resolved by instead preventing the selection of headers < 5.4.0 on RISC-V 32-bit, but that is difficult to do as the user can choose a custom header version, or simply specific that (s)he wants to use the headers of the kernel being built. In those situations, it's difficult to prevent selecting headers < 5.4.0. Prevent random configurations from triggering a build failure in our autobuilders, by excluding that symbol from accepted configuration. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> [yann.morin.1998@free.fr: update genrandconfig] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> |
||
|---|---|---|
| arch | ||
| board | ||
| boot | ||
| configs | ||
| docs | ||
| fs | ||
| linux | ||
| package | ||
| support | ||
| system | ||
| toolchain | ||
| utils | ||
| .clang-format | ||
| .defconfig | ||
| .flake8 | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .shellcheckrc | ||
| 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 OFTC IRC. If you would like to contribute patches, please read https://buildroot.org/manual.html#submitting-patches