commit | 9b41febad78c45477a293ac7e06e2879247b978b | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Wed Jul 13 10:24:16 2022 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Wed Jul 13 10:24:16 2022 -0500 |
tree | 6e36c5f477dabcc45af9508f006e5e4b6989d1dd | |
parent | a9f85590e8e39f1a66f0160d8ac63910c030d0af [diff] |
Revert clang-format to align with openbmc/docs Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I50db2f1021b7f55711ad9bdcc318f63ce4109c62
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