remove old Boost workaround #3604

pull Diapolo wants to merge 1 commits into bitcoin:master from Diapolo:boost-worka changing 1 files +0 −11

Diapolo commented at 10:02 AM on January 30, 2014: none

No description provided.
remove old Boost workaround 1cbbca3418
BitcoinPullTester commented at 10:54 AM on January 30, 2014: none

Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/1cbbca3418d76b9209493131f292f1bc9ebb25f0 for binaries and test log. This test script verifies pulls every time they are updated. It, however, dies sometimes and fails to test properly. If you are waiting on a test, please check timestamps to verify that the test.log is moving at http://jenkins.bluematt.me/pull-tester/current/ Contact BlueMatt on freenode if something looks broken.
luke-jr commented at 6:38 PM on January 30, 2014: member

What harm is there in leaving this? Why would we drop support for whatever platform(s) need it?
laanwj commented at 7:30 AM on January 31, 2014: member

Agreed, there's no harm in leaving this for now.
Diapolo commented at 7:37 AM on January 31, 2014: none

Thought we could cleanup old stuff because we recently switched to more recent Boost versions.
Diapolo closed this on Jan 31, 2014
luke-jr commented at 7:42 AM on January 31, 2014: member

Switching versions for Windows binaries does not mean mandating newer dependencies for the code itself.
laanwj commented at 8:14 AM on January 31, 2014: member

What we ship with gitian are the recommended dependency versions. The minimum required dependency versions shouldn't be bumped unless really necessary. This is because "stable"/"enterprise" linux distributions tend to have very old versions of dependencies. The same for tool chains for old versions of OSX (in the case of this LLVM workaround).
Diapolo deleted the branch on Feb 10, 2014
DrahtBot locked this on Sep 8, 2021

Contributors