Consider providing a second source to download Boost library in build script

[b1aafulei]

When the Boost library is not present in the local machine, the current build script will download it from bintray.com where the boost-org chooses to distribute the library.

eos/scripts/helpers/eosio.sh

Line 257 in 8ac99b2

curl -LO https://dl.bintray.com/boostorg/release/$BOOST_VERSION_MAJOR.$BOOST_VERSION_MINOR.$BOOST_VERSION_PATCH/source/boost_$BOOST_VERSION.tar.bz2 \

However, it is a recurring problem that towards the end of a month boost-org will reach their "bandwidth limit at bintray for the month" 😅 (see the related issue here).

It is another month end now, so I met this problem again.

This instantly stops the installation for the EOSIO software.

It is not a fault by EOSIO but I would like to flag it.

In the future maybe we shall consider providing a second source to download the Boost library for back-up, for example, from sourceforge.

[heifner]

Also hit this today. Thanks for pointing out the issue.

[heifner]

I grabbed it from here: https://sourceforge.net/projects/boost/files/boost/1.72.0/boost_1_72_0.tar.gz/download

[spoonincode]

Funny enough, the 1.71.0 source files have been removed from sourceforge. 1.71 is our target version for 2.0.x scripts & builds.