11 Commits (81c89e966e1e08c3d94dc9d1d0a26034312c56ff)

Author	SHA1	Message	Date
fanquake	d78269ac99	[depends] Boost 1.64.0	8 years ago
fanquake	4ed6faf381	[depends] Boost 1.63.0	8 years ago
fanquake	16f8823088	[depends] Boost 1.61.0	8 years ago
Cory Fields	a398549b3b	depends: use c++11	9 years ago
fanquake	9e940fa4c6	[depends] Boost 1.59.0	9 years ago
Cory Fields	4bdad99f50	depends: bump boost to 1.58.0	10 years ago
Jacob Welsh	b19a88b2a0	depends: fix Boost 1.55 build on GCC 5 ... 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: eec8085549 See also: https://svn.boost.org/trac/boost/ticket/10500	10 years ago
Cory Fields	4302fa67b1	depends: Use pic for all linux dependencies ... This avoids textrels, and matches previous gitian behavior.	10 years ago
Cory Fields	0246ab6088	depends: boost: hard-code hidden symbol visibility ... 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.	10 years ago
Cory Fields	3b63df5fac	depends: boost: build for debug or release as requested ... Also hook up cppflags there, which was missing before.	10 years ago
Cory Fields	1dec09b341	depends: add shared dependency builder ... See the README's in depends for documentation	10 years ago