I've done a rebuild of 0.20.1 and I get the same results that you do. This would indicate that a build dependency has updated to produce slightly different results than the version that was in use at the time of the release. The build dependency versions are pinned unlike the actual software dependencies. IIRC this is common for gitian builds and attempting ...
Because checking for compiler features, without Automake/CMake/Ninja/Bazel with only Makefile and C++ preprocessor is hard and unelegant.
And C++ preprocessor can't be used to make full-compile feature tests. If the compiler supports AVX256, a relatively new instruction set, that doesn't mean the assembler supports it too. There are "fail if can't ...
By default, yes and no.
No, most of the code is compiled for generic target hardware. If you want something optimized for your actual hardware, you can add -march=native to your compilation flags (e.g. you'd run ./configure CFLAGS="-march=native" CXXFLAGS="-march=native"). This will result in a binary that may not work on other hardware ...
Berkeley-db from brew which is clang compiled is GCC incompatible. Either Recompile berkeley-db4 with GCC:
HOMEBREW_CC=gcc-10 HOMEBREW_CXX=g++-10 brew reinstall --build-from-source berkeley-db4
or compile Core with clang
The two points raised in the comments are necessary to compile bitcoin core v0.10.0. First the best way to install Boost libraries in unix is described in build_unix.md, where in the Boost section we have
but for v0.10.0 we need at least version 1.57 of Boost that can be found here.
We will also need older versions of ...
Any sites, forums dedicated to developers new to bitcoin
And if you your question is closed here then, https://reddit.com/r/bitcoin
IRC: #bitcoin-core-pr-reviews IRC channel on freenode
Slack: https://bitcoincore.slack.com, https://lightningdevkit.slack.com, https://lightningcommunity.slack.com and https://suredbits.slack....
As long as the underlying OS image is susceptible to changes, you will not get a reproducible build system that guarantees reproducibility over a long period of time. If the OS can update compiler toolchains, libc versions and whatever tools are used during a gitian build, changes in the future to the output are expected. Since this is the case since gitian ...