diff options
author | Laszlo Ersek <lersek@redhat.com> | 2018-03-07 10:17:28 +0100 |
---|---|---|
committer | Laszlo Ersek <lersek@redhat.com> | 2018-03-07 22:42:55 +0100 |
commit | 777f4aa083e9f8b1853e454a0390d71dde2616da (patch) | |
tree | a0aeb80098d7d9898776d3ea6df048c5f1e11d94 /BaseTools/Source/Python | |
parent | 4cc2b63bd829426b05bad0d8952f1855a10d6ed7 (diff) | |
download | edk2-777f4aa083e9f8b1853e454a0390d71dde2616da.tar.gz edk2-777f4aa083e9f8b1853e454a0390d71dde2616da.tar.bz2 edk2-777f4aa083e9f8b1853e454a0390d71dde2616da.zip |
BaseTools/header.makefile: revert gcc-8 "-Wno-xxx" options on OSX
I recently added the gcc-8 specific "-Wno-stringop-truncation" and
"-Wno-restrict" options to BUILD_CFLAGS, both for "Darwin" (XCODE5 /
clang, OSX) and otherwise (gcc, Linux / Cygwin).
I also regression-tested the change with gcc-4.8 on Linux -- gcc-4.8 does
not know either of the (gcc-8 specific) "-Wno-stringop-truncation" and
"-Wno-restrict" options, yet the build completed fine (by GCC design).
Regarding OSX, my expectation was that
- XCODE5 / clang would either recognize these warnings options (because
clang does recognize most -W options of gcc),
- or, similarly to gcc, clang would simply ignore the "-Wno-xxx" flags
that it didn't recognize.
Neither is the case; the new flags have broken the BaseTools build on OSX.
Revert them (for OSX only).
Cc: Liming Gao <liming.gao@intel.com>
Cc: Yonghong Zhu <yonghong.zhu@intel.com>
Reported-by: Liming Gao <liming.gao@intel.com>
Fixes: 1d212a83df0eaf32a6f5d4159beb2d77832e0231
Fixes: 9222154ae7b3eef75ae88cdb56158256227cb929
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Laszlo Ersek <lersek@redhat.com>
Reviewed-by: Liming Gao <liming.gao@intel.com>
Acked-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Diffstat (limited to 'BaseTools/Source/Python')
0 files changed, 0 insertions, 0 deletions