mirror of
https://github.com/bitcoin/bitcoin.git
synced 2025-02-09 10:43:19 -05:00
![]() The actual macro is __has_include(), not __has_include__(), using the later would result in build failures when using GCC 10. i.e: ```bash ../sysdeps/unix/sysv/linux/riscv/flush-icache.c:24:5: warning: "__has_include__" is not defined, evaluates to 0 [-Wundef] 24 | #if __has_include__ (<asm/syscalls.h>) ``` Looks like at least someone else has run into the same thing, see: http://lists.busybox.net/pipermail/buildroot/2020-July/590376.html. See also: https://gcc.gnu.org/onlinedocs/cpp/_005f_005fhas_005finclude.html https://clang.llvm.org/docs/LanguageExtensions.html#has-include |
||
---|---|---|
.. | ||
elfsteem-value-error-python-39.patch | ||
gcc-broken-longjmp.patch | ||
glibc-2.24-elfm-loadaddr-dynamic-rewrite.patch | ||
glibc-2.24-no-build-time-cxx-header-run.patch | ||
glibc-2.27-riscv64-Use-__has_include-to-include-asm-syscalls.h.patch | ||
glibc-ldd-x86_64.patch | ||
glibc-versioned-locpath.patch | ||
nsis-gcc-10-memmove.patch | ||
oscrypto-hard-code-openssl.patch | ||
vmov-alignment.patch |