commit | eea45427d3c5976f1922711cf01a0e25ca193993 | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Thu Apr 15 10:54:14 2021 -0500 |
committer | ben.tyner <ben.tyner@ibm.com> | Thu Apr 15 21:03:57 2021 +0000 |
tree | 85ca4b60c171fffbe57a06030396d31f1e5fe1e3 | |
parent | 2d5c63d90c14793e333c4eee6d0b8002fdf0c7ba [diff] |
Attn: Add build info to binary Build information will be generated and embedded into the binary. This info will be displayed in the help text when you execute the binary without any command line options. This change has a libhei dependency. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I8caf1694f5b656557aa862eefb77b88d0b892d41
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