Boost iostreams was picking up zlib in some build environments.
We do not need zlib support in boost::iostreams so disable it.
This normalizes the gitian boost build between build environments by forcing a setting instead of auto-detecting.
Fixes the non-deterministic issue in #3725
Boost iostreams was picking up zlib in some build environments.
We do not need zlib support in boost::iostreams so disable it.
This normalizes the gitian boost build between build environments
by forcing a setting instead of auto-detecting.
Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/c651070663a09e2759239097d4561aec952dd641 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.
I'm going to fix this the other way around: enable libz-dev for all boost linux builds. Less script impact, and having zlib support in iostreams may be useful some day.