commit | c3fb20620d16997dcd30b964617cd98469de3941 | [log] [tgz] |
---|---|---|
author | Caleb Palmer <cnpalmer@us.ibm.com> | Fri Feb 04 15:10:59 2022 -0600 |
committer | Caleb Palmer <cnpalmer@us.ibm.com> | Fri Feb 04 15:22:05 2022 -0600 |
tree | 600bdf784a9cd728345a6c610264693768c1e3fa | |
parent | 55e7fec3b6fc836749ad5f57b6213074ce29324b [diff] |
Cast SrcSubsystem to uint8_t before passing to fmt::format Signed-off-by: Caleb Palmer <cnpalmer@us.ibm.com> Change-Id: Ic9c62d0120ca6cac5a512dba653fcc93e830aa24
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