c41a06bbd9
When running check-package before completing commits for a change, if any files are setup for removal, check-package will throw FileNotFoundError exceptions instead of generating a warning state. For example: $ utils/docker-run make check-package Traceback (most recent call last): ... FileNotFoundError: [Errno 2] No such file or directory: 'package/.../0001-some-removed-patch.patch' make: *** [Makefile:1264: check-package] Error 1 This commit will now catch FileNotFoundError and populate a warning message: $ utils/docker-run make check-package package/.../0001-some-removed-patch.patch: missing; unstaged file removal? package/.../0002-another-removed-patch.patch: missing; unstaged file removal? 427843 lines processed 3 warnings generated make: *** [Makefile:1264: check-package] Error 1 Signed-off-by: James Knight <git@jdknight.me> Reviewed-by: Romain Naour <romain.naour@smile.fr> Signed-off-by: Julien Olivain <ju.o@free.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