aboutsummaryrefslogtreecommitdiff
path: root/depends/packages/boost.mk
AgeCommit message (Collapse)Author
2017-01-11[depends] Boost 1.63.0fanquake
2016-09-27[depends] Boost 1.61.0fanquake
2016-04-27depends: use c++11Cory Fields
2015-11-10[depends] Boost 1.59.0fanquake
2015-07-03depends: bump boost to 1.58.0Cory Fields
2015-06-13depends: fix Boost 1.55 build on GCC 5Jacob Welsh
Boost assumes variadic templates are always available in GCC 4.4+, but they aren't since we don't build with -std=c++11. This applies the patch that fixed the issue in boost 1.57: https://github.com/boostorg/config/commit/eec808554936ae068b23df07ab54d4dc6302a695 See also: https://svn.boost.org/trac/boost/ticket/10500
2014-11-19depends: Use pic for all linux dependenciesCory Fields
This avoids textrels, and matches previous gitian behavior.
2014-11-05depends: boost: hard-code hidden symbol visibilityCory Fields
tl;dr: This solves boost visibility problems for default/release build configs on non-Linux platforms. When Bitcoin builds against boost's header-only classes, it ends up with objects containing symbols that the upstream boost libs also have. Since Bitcoin builds by default with hidden symbol visibility, it can end up trying to link against a copy of the same symbols with default visibility. This is not a problem on Linux because 3rd party static libs are un-exported by default (--exclude-libs,ALL), but that is not available for MinGW and OSX. Those platforms (and maybe others?) end up confused about which version to use. The OSX linker spews hundreds of: "ld: warning: direct access in <foo> to global weak symbol guard variable for <bar> means the weak symbol cannot be overridden at runtime. This was likely caused by different translation units being compiled with different visibility settings." MinGW's linker complains similarly. Since the default symbol visibility for Bitcoin is hidden and releases are built that way as well, build Boost with hidden visibility. Linux builds Boost this way also, but only for the sake of continuity. This means that the linker confusion logic is reversed, so the problem will will now be encountered if Bitcoin is built with --disable-reduce-exports, but that's better than the current situation.
2014-09-25depends: boost: build for debug or release as requestedCory Fields
Also hook up cppflags there, which was missing before.
2014-08-08depends: add shared dependency builderCory Fields
See the README's in depends for documentation