b3ba26150d
The custom external toolchain logic asks the user to specify which gcc version is provided by the toolchain. The list of gcc versions given by Buildroot is restricted depending on the selected CPU architecture using the BR2_ARCH_NEEDS_GCC_AT_LEAST_xyz config options. However, these config options generally indicate in which upstream gcc version the support for the selected architecture was introduced. But in practice, it is possible that an external toolchain uses some non-upstream gcc code, providing support for a CPU architecture before it was merged in upstream gcc. A specific example is that there are pre-built external toolchains for the C-SKY CPU architecture that are based on gcc 6.x, even if the support for it was only added in upstream gcc 9.x. Due to the BR2_ARCH_NEEDS_GCC_AT_LEAST_xyz options, only gcc >= 9.x can be selected for C-SKY, preventing the use of such a custom toolchain. In addition, those dependencies are in fact not really needed: Buildroot will check that the gcc version provided matches what the user declared in the configuration. And if the gcc provided by the toolchain does support that CPU architecture, then well, so be it, there's no need to restrict the gcc version selected. So we simply get rid of these dependencies on BR2_ARCH_NEEDS_GCC_AT_LEAST_xyz, and also don't use them anymore to chose a default value for the gcc version. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Yann E. MORIN <yann.morin.1998@free.fr> Acked-by: Yann E. MORIN <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.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