commit | f36466f4486d1e34d8c9927abeded69d8ac57b80 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Fri Feb 11 15:10:55 2022 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Fri Feb 11 15:12:43 2022 -0600 |
tree | 777667a768490fb5b19f882b18a2f33cab7f7c2c | |
parent | 97bdac4ccc7581c8c159f54cb7f7d48fb8a0b765 [diff] |
Header file cleanup in attn Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I0a6d608860c3c24b3aa0bc2b69b89d651a3eb9b5
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