commit | 659e65cf16807f701ad82edc37fb50e4af984ced | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Wed Jul 21 09:49:35 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Fri Jul 23 22:09:51 2021 +0000 |
tree | fd96347ee9848ab3274548f71edb213482c3a2cd | |
parent | b83355686bc23400c5cf7988e0570fd13da20777 [diff] |
util:dbus: Limit the scope of some variables The scope of some variables were reduced in response to CI compiler warnings. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: Ia3bcccc2f2aeff70dad3d835a4c2e912c2ebeefb
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