crasbe

I think this had some unintended side-effects: All the block comments are now incorrectly formatted 👀

You're welcome :)

I'll run it on my work computer tomorrow, then you can address the suggestions without triggering a full rebuild on every fixup.

This is the result for `generate-Makefile.ci` for your example: ```makefile BOARD_INSUFFICIENT_MEMORY := \ bluepill-stm32f030c8 \ i-nucleo-lrwan1 \ nucleo-c031c6 \ nucleo-f030r8 \ nucleo-f031k6 \ nucleo-f042k6 \ nucleo-l011k4 \ nucleo-l031k6 \ nucleo-l053r8...

I think the reason for the build failure is that `MCPU` is defined *after* it's being added to the CFLAGS and not evaluated correctly. The sanatation of the `CFLAGS` likely...

Is #20581 potentially the solution for this? I don't have a board with a STM32F767ZI, so I can't really test if it is still an issue.

It would be nice if we could move this forward :)

I think the build system considers the out-of-tree test folder as a dedicated application: ``` buechse@skyleaf:~/RIOTstuff/riot-vanillaice/RIOT$ make info-applications | grep tests/build_system/external_unittests tests/build_system/external_unittests tests/build_system/external_unittests/external_tests_dir/tests-out_of_tree tests/build_system/external_unittests/tests-in_tree ``` And since `$(RIOTBASE)` is undefined...

By the way... how do you test these locally? They aren't pushed to `docker.io` yet obviously, so the FROM statement fails. I played around with it yesterday but didn't get...

I got it working with the aforementioned changes and my PR applied with the following modification: ```diff diff --git a/makefiles/docker.inc.mk b/makefiles/docker.inc.mk index fee33ac013..8ec546c8a0 100644 --- a/makefiles/docker.inc.mk +++ b/makefiles/docker.inc.mk @@ -8,7...