commit | 2923775f8356cc58e93a3e8d5d70958253de3808 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Wed Dec 22 11:00:30 2021 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Wed Dec 22 11:00:30 2021 -0600 |
tree | 8e5afc76619cf72514a3646b5719096f63b5b938 | |
parent | 8018391d05873634c1771ebfffca398b30d7ca90 [diff] |
update to C++20 Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I6958180551f4a8265be57661844a81d9441f086e
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