mirror of
https://gitlab.com/buildroot.org/buildroot.git
synced 2026-10-18 23:01:50 -09:00
9d2c262030
There's recently been autobuilder failures on toolchain-external-bootlin, but I wasn't getting notified in the daily autobuilder e-mail for those failures, which sounded odd as DEVELOPERS contains: N: Thomas Petazzoni <thomas.petazzoni@bootlin.com> [...] F: toolchain/ And indeed, testing: $ ./utils/get-developers -p toolchain-external-bootlin returned nothing. Turns out that the regexp FIND_INFRA_IN_PATCH and FIND_INFRA_IN_MK used to find the package infrastructure, and ultimately decide if a given .mk file contains a package, was a bit too strict: "^\+\$\(eval \$\((host-)?([^-]*)-package\)\)$" This would only allow packages named <something>-package or host-<something>-package, but the <something> should not contain any dash ("-"). So this works fine for cmake-package, host-autotools-package, but not for toolchain-external-package where <something> is toolchain-external and it contains a dash. We fix this by relaxing the regexp a bit and allowing any character in <something>. Consider the rest of the regexp that expects $(eval $(<host>-<something>-package)), it seems highly unlikely to match anything else but the line we're interested in. With this fix: $ ./utils/get-developers -p toolchain-external-bootlin Giulio Benetti <giulio.benetti@benettiengineering.com> Romain Naour <romain.naour@gmail.com> Thomas Petazzoni <thomas.petazzoni@bootlin.com> This issue has existed since the toolchain-external-package infrastructure had been added. Fixes:1c99d70e52("toolchain-external: introduce toolchain-external-package") Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Julien Olivain <ju.o@free.fr> (cherry picked from commit592d5c517e) Signed-off-by: Raphaël Mélotte <raphael.melotte@mind.be>
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 https://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