commit | 0577c0137f4d262789bca87f2ba0feac88654011 | [log] [tgz] |
---|---|---|
author | Ed Tanous <edtanous@google.com> | Wed Mar 01 11:18:36 2023 -0800 |
committer | Zane Shelley <zshelle@us.ibm.com> | Wed Mar 01 23:01:57 2023 +0000 |
tree | 027fd3f64da8669528402da4cad75f84dcc76593 | |
parent | d5fa958419584f1742c67f5276dc534531bfbfe9 [diff] |
Change io_service to io_context This was renamed a while back in boost to be compliant with the std::executors proposal. Change-Id: I67eb15038f2aa6957738fa5e3f6c14fd66460b7a Signed-off-by: Ed Tanous <edtanous@google.com>
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