33ecdd7389
Currently, we are enforcing the _FORTIFY_SOURCE=2 without any previous detection if the macro has been already defined, e.g. by environment, or is just enabled by compiler by default on some distributions (e.g. Gentoo). This could result in the error like this: <command-line>:0:0: error: "_FORTIFY_SOURCE" redefined [-Werror] <built-in>: note: this is the location of the previous definition Tracked-On: #2344 Signed-off-by: Tw <wei.tan@intel.com> Reviewed-by: Binbin Wu <binbin.wu@intel.com> Acked-by: Yin Fengwei <fengwei.yin@intel.com> |
||
|---|---|---|
| .. | ||
| acrn-crashlog | ||
| acrn-manager | ||
| acrnbridge | ||
| acrnlog | ||
| acrntrace | ||
| Makefile | ||
| README.rst | ||
README.rst
ACRN tools ########## The open source `Project ACRN`_ defines a device hypervisor reference stack and an architecture for running multiple software subsystems, managed securely, on a consolidated system by means of a virtual machine manager. It also defines a reference framework implementation for virtual device emulation, called the “ACRN Device Model”. This folder holds the source to a number of tools that facilitate the management, debugging, profiling, and logging of multi-OS systems based on ACRN. You can find out more about Project ACRN and its set of tools on the `Project ACRN documentation`_ website. .. _`Project ACRN`: https://projectacrn.org .. _`Project ACRN documentation`: https://projectacrn.github.io/