commit | f80482a5017a898ee69fec57d15a6201a6fcbbd5 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Wed Dec 02 15:13:13 2020 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Wed Dec 02 15:13:13 2020 -0600 |
tree | f22917bc5ee90a2087b41fd769052f4b4fd069ea | |
parent | 9faf73bae8d4f62d3adda153d407992a2251f655 [diff] |
Create util static library Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I72926c6aad2468f2f8b32685dc03b7d5004871f0
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