commit | 4efca2808c4221a17e7b7483df1ec7751b2873e7 | [log] [tgz] |
---|---|---|
author | Andrew Geissler <geissonator@yahoo.com> | Fri Jun 10 09:12:30 2022 -0400 |
committer | Andrew Geissler <geissonator@yahoo.com> | Fri Jun 10 09:13:43 2022 -0400 |
tree | f6db6a024bacd719ff30446ea89b59b6b19277c3 | |
parent | ed3ab8f95d20ebe533f75f135425df198a2b870a [diff] |
include what you use (array) New yocto rebase compiler has been failing on missing includes so add them in. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: Iebd2fcc5d248528e04d3c58b4d4ecd2f5694f4aa
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