commit | ed3ab8f95d20ebe533f75f135425df198a2b870a | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Tue May 24 21:08:21 2022 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue May 24 21:08:21 2022 -0500 |
tree | 6e916019b8f7b4a7ff72e44ee772749cdb77611d | |
parent | cd6373d34e0f38965f3650d3da98d0744bb6ecf3 [diff] |
Fix outdate comment in analyzer filter support Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I5e14eb82a4017ed794314d2800ea88dd0d706942
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