On Tue, 2022-09-27 at 19:02 -0700, Khem Raj wrote:

On Tue, Sep 27, 2022 at 3:41 PM Edgar Mobile <heideggm@...>
wrote:

Yeah building gcc alone worked.
Now I'm concerned about the health of my machine.
Thank you!

Your machine is fine I think bitbake is extremely parallel and that
might be issue that it’s eating up all the memory. How many cores
does this machine have? And ram ? Usually it’s good to keep 3-4gb ram
per core for default operations you can also pin how much parallels
tasks and -j settings bitbake should use during build look for
PARALLEL_MAKE documentation 

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.

Cheers,

Richard