diff options
| author | fanquake <fanquake@gmail.com> | 2020-12-19 16:09:18 +0800 |
|---|---|---|
| committer | fanquake <fanquake@gmail.com> | 2020-12-20 21:43:58 +0800 |
| commit | e9189a750b237eba1befc6b16c12c2cee3e0176c (patch) | |
| tree | 68c32d66054f8dc7361e2aa684b30bdb1bceabe1 /configure.ac | |
| parent | f1dbf92ff0475a01d20170ea422c1d086acbbc57 (diff) | |
| download | bitcoin-e9189a750b237eba1befc6b16c12c2cee3e0176c.tar.xz | |
build: more robustly check for fcf-protection support
When using Clang 7, we may end up trying to use the flag when it won't
work properly, which can lead to confusing errors. i.e:
```bash
/usr/bin/ld: error: ... <corrupt x86 feature size: 0x8>
```
Use CHECK_LINK_FLAG & --fatal-warnings to ensure we wont use the flag in this case.
Diffstat (limited to 'configure.ac')
| -rw-r--r-- | configure.ac | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/configure.ac b/configure.ac index 97bb6d8bd2..d50603458d 100644 --- a/configure.ac +++ b/configure.ac @@ -819,7 +819,10 @@ if test x$use_hardening != xno; then AX_CHECK_COMPILE_FLAG([-Wstack-protector],[HARDENED_CXXFLAGS="$HARDENED_CXXFLAGS -Wstack-protector"]) AX_CHECK_COMPILE_FLAG([-fstack-protector-all],[HARDENED_CXXFLAGS="$HARDENED_CXXFLAGS -fstack-protector-all"]) - AX_CHECK_COMPILE_FLAG([-fcf-protection=full],[HARDENED_CXXFLAGS="$HARDENED_CXXFLAGS -fcf-protection=full"]) + dnl -fcf-protection used with Clang 7 causes ld to emit warnings: + dnl ld: error: ... <corrupt x86 feature size: 0x8> + dnl Use CHECK_LINK_FLAG & --fatal-warnings to ensure we wont use the flag in this case. + AX_CHECK_LINK_FLAG([-fcf-protection=full],[HARDENED_CXXFLAGS="$HARDENED_CXXFLAGS -fcf-protection=full"],, [[$LDFLAG_WERROR]]) dnl stack-clash-protection does not work properly when building for Windows. dnl We use the test case from https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90458 |