README: start a section for documenting CFLAGS

Start a section in the README for documenting that custom CFLAGS yields
custom results and that your mileage may vary. The first CFLAG to
document that you likely want to include is -fno-semantic-interposition.

Signed-off-by: William Roberts <william.c.roberts@intel.com>
Acked-by: Stephen Smalley <stephen.smalley.work@gmail.com>
This commit is contained in:
William Roberts 2020-06-08 17:38:16 -05:00 committed by Petr Lautrbach
parent 7ad84e7c8d
commit ddcd6d1b73
1 changed files with 11 additions and 0 deletions

View File

@ -120,6 +120,17 @@ lacks library functions or other dependencies relied upon by your
distribution. If it breaks, you get to keep both pieces. distribution. If it breaks, you get to keep both pieces.
## Setting CFLAGS
Setting CFLAGS during the make process will cause the omission of many defaults. While the project strives
to provide a reasonable set of default flags, custom CFLAGS could break the build, or have other undesired
changes on the build output. Thus, be very careful when setting CFLAGS. CFLAGS that are encouraged to be
set when overriding are:
- -fno-semantic-interposition for gcc or compilers that do not do this. clang does this by default. clang-10 and up
will support passing this flag, but ignore it. Previous clang versions fail.
macOS macOS
----- -----