commit | dd779995caa24b654da52fac79bae08a4d1474c3 | [log] [tgz] |
---|---|---|
author | austinfcui <austinfcui@gmail.com> | Fri Mar 25 21:13:18 2022 -0500 |
committer | austinfcui <austinfcui@gmail.com> | Mon Mar 28 11:49:30 2022 -0500 |
tree | 162f94a0e74a772d22721a63f394037d05255802 | |
parent | ab1e4dda8239b54920ff1a38bde4b1f58b0d322b [diff] |
Check existing temp files in system's temp folder Signed-off-by: austinfcui <austinfcui@gmail.com> Change-Id: Ic76c058cb18d5e723794a86c6695b73fbc409fa3
In the event of a system fatal error reported by the internal system hardware (processor chips, memory chips, I/O chips, system memory, etc.), POWER Systems have the ability to diagnose the root cause of the failure and perform any service action needed to avoid repeated system failures.
Aditional details TBD.
For a standard OpenBMC release build, you want something like:
meson -Dtests=disabled <build_dir> ninja -C <build_dir> ninja -C <build_dir> install
For a test / debug build, a typical configuration is:
meson -Dtests=enabled <build_dir> ninja -C <build_dir> test