commit | 710101c03fee69d998e3596cc02574ee495d19ad | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Tue Feb 13 21:37:47 2024 -0600 |
committer | Patrick Williams <patrick@stwcx.xyz> | Tue Feb 13 21:37:49 2024 -0600 |
tree | 180e8f814ba4f7ede6bc7a528f2c390a09fefc7a | |
parent | b7d37e991e8a3c7ad74e1e7c8e2f85e735aacfc5 [diff] |
prefer std::format over fmt Switch to use std::format and remove the fmt dependency. Change-Id: I321722ea3009350665549a065fc1cc1085b01ccd Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
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