[Buildroot] Some analysis of the major build failure reasons
Arnout Vandecappelle
arnout at mind.be
Tue Aug 3 14:41:20 UTC 2021
On 03/08/2021 12:11, Thomas Petazzoni wrote:
> Hello,
>
> On Tue, 3 Aug 2021 12:04:13 +0200
> Arnout Vandecappelle <arnout at mind.be> wrote:
>
>> A simpler solution is to use 'make -Orecurse' or 'make -Otarget'. That keeps
>> the recursive output together.
>
> True, but as you say below, it doesn't guarantee that the actual issue
> appears in the last part of the build log.
>
>> It may not fully help due to the "Waiting for unfinished jobs" bit - the line
>> with the failed package may appear just before that. But that can be solved by
>> first searching the "Waiting for unfinished jobs" line and cutting off
>> everything after it.
>
> True. Needs some logic in extract_end_log() in autobuild-run.
>
> So what should we do ? Build with -Otarget, and keep the last ~500
> lines before the "Waiting for unfinished jobs" ?
Yeah, I think that's the way to go. Not sure if -Orecurse or -Otarget is the
way to go though, I'm still a bit fuzzy on their respective effects...
Regards,
Arnout
>
>> Additional autobuilders do help because they offer a different build
>> environment. If there's some autobuild failure that *doesn't* happen on James's
>> machines, you can be sure that it's due to the build environment.
>
> Absolutely true, that's a very good point that you have here.
>
> Thomas
>
More information about the buildroot
mailing list