mirror of
https://gitlab.com/buildroot.org/buildroot.git
synced 2026-09-09 07:51:59 -09:00
7724268034
gcc 15 was introduced in Buildroot in commit [1]. In Buildroot, a user creates a build configuration in Kconfig menus by selecting the CPU architecture and CPU first, then a toolchain that support this CPU, then packages and system configuration. To make sure those Kconfig menus and choices behave correctly in that order, we use a logic in which a CPU selects the Kconfig symbol BR2_ARCH_NEEDS_GCC_AT_LEAST_N (with N being the needed gcc version). Then, to make sure unsupported gcc version are hidden for a selected CPU, a gcc version N has in fact a "depends on !BR2_ARCH_NEEDS_GCC_AT_LEAST_(N+1)". For example, Cortex-A710 needs at least gcc 12. See [2] and [3]. This means that when we introduce the latest gcc version with this logic in place, we already need this BR2_ARCH_NEEDS_GCC_AT_LEAST_(N+1) symbol defined. Doing so is desirable to avoid forgetting to add it later. See for example commit [4], adding those missing dependencies for gcc 13 and 14. Since in Buildroot we currently keep 3 actively maintained gcc versions, adding a new gcc version N in Buildroot should: - add the BR2_ARCH_NEEDS_GCC_AT_LEAST_(N+1) symbol - add package/gcc N - switch the default gcc from N-2 to N-1 - drop package/gcc N-3 Then, once this new gcc N is added, new CPUs supported by that version can be introduced, by selecting BR2_ARCH_NEEDS_GCC_AT_LEAST_N. All this logic will be ready for future gcc versions. This was also described in commit log [5]. This commit simply adds the BR2_ARCH_NEEDS_GCC_AT_LEAST_16 symbol. It is worth mentioning that, at the time of this commit, gcc 16 is not released yet. This release number 16 is already known, though. See [6]. For reference, this was discussed in [7]. [1]75891397ab[2] https://gitlab.com/buildroot.org/buildroot/-/blob/2025.05/arch/Config.in.arm#L514 [3] https://gitlab.com/buildroot.org/buildroot/-/blob/2025.05/package/gcc/Config.in.host#L27 [4]6f231d3003[5]eab17d763c[6] https://gcc.gnu.org/gcc-16/changes.html [7] https://lore.kernel.org/buildroot/877c0v1sn1.fsf@dell.be.48ers.dk/T/#m45688e25632401029e4c0d989072e1d3e1a59854 Signed-off-by: Julien Olivain <ju.o@free.fr> Signed-off-by: Romain Naour <romain.naour@smile.fr>
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