Re: Builing Gcc fails Poky
On Tue, 2022-09-27 at 19:02 -0700, Khem Raj wrote:
Khem may be right and it may simply be running out of memory. You could
have a look in dmesg and see if the kernel did report OOM conditions.
What worries me a little bit is that things corrupted. It is possible
that OOM could do that but that would mean exit code checking isn't
happening properly somewhere along the line in the gcc build system
itself (which is possible) or there is some other issue with the error
code paths. The underlying software build systems are really outside
YP's scope though.