commit | 9fb657f9bac9adf2bad14ebfc564b2660f5cd275 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Tue Jan 12 15:30:58 2021 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Jan 12 16:08:51 2021 -0600 |
tree | c70ec0e718c5576826117d9f71c81a4506cef5ca | |
parent | f5210bb662ad7e41a4184d9dca12b8000ab3a03a [diff] |
Proper handling for unused parameters Instead of ignoring the parameter warning via a compile flag we can explicitly not give the parameter a valiable name. The compile will then know that that the parameter is not expected to be used. Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Idfc9c7b2ac9e2f6a3d220540a354b1b8e890bee8
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