As far as I understand, the compilation of a given configuration stops at the first compilation error.
And now we know that several bugs can be present in a configuration.
So it's worth compiling as much as we can to gather additional compilation errors / failure messages.
Some ideas:
use make -k (or --keep-going on gnumake)
we have an internal mechanism that retries the compilation (using apt-file search over the log message error)
[ ] check the assumption "the compilation of a given configuration stops at the first compilation error" using Docker env., some representative configurations (.config), and then a manual configuration (not using the internal mechanism)
As far as I understand, the compilation of a given configuration stops at the first compilation error. And now we know that several bugs can be present in a configuration. So it's worth compiling as much as we can to gather additional compilation errors / failure messages.
Some ideas:
use make -k (or --keep-going on gnumake)
we have an internal mechanism that retries the compilation (using apt-file search over the log message error)
[ ] check the assumption "the compilation of a given configuration stops at the first compilation error" using Docker env., some representative configurations (.config), and then a manual configuration (not using the internal mechanism)