-
Notifications
You must be signed in to change notification settings - Fork 2.3k
error: downloading 'https://dl.bintray.com/boostorg/release/1.66.0/source/boost_1_66_0.7z' failed #2290
Comments
This PR is used to fix the issue error: downloading 'https://dl.bintray.com/boostorg/release/1.66.0/source/boost_1_66_0.7z' failed ethereum-mining#2290 The original hunter is ruslo/hunter is not maintained. The link of boost included in it is unavailable now. So, update the cpp_pm/hunter to fix the boost link issue.
As ruslo/hunter is obsolete we replace this with cpp-pm/hunter Please find below mentioned piece of CMakeList.txt. But after this change we ended up with below mentioned error: CMake Error at src/jsonrpccpp/CMakeLists.txt:144 (add_library): -- Generating done [hunter ** FATAL ERROR **] Build step failed (dir: /home/s2600bottom/.hunter/_Base/1151d53/53fea1f/4646e4e/Build/libjson-rpc-cpp ------------------------------ ERROR -----------------------------
|
Try this change: 4734802 |
its work for me: |
^^ This is the only change needed to get past this step |
The solution works perfectly. Please merge |
git clone https://github.com/ethereum-mining/ethminer.git How get SHA1 for boost_1.67.0: |
Worked for me |
and why this hasnt being merged? |
I guess this repo needs some more maintainers 🤔 |
I have this problem also. Is it merged yet? |
Why hasn't it merged yet? |
same! |
I have solved it here #2413 by updating the hunter to the working version |
When build, there is error to prepare hunter:
error: downloading 'https://dl.bintray.com/boostorg/release/1.66.0/source/boost_1_66_0.7z' failed
To Reproduce
Steps to reproduce the behavior:
cmake .. -DETHASHCL=OFF -DBINKERN=OFF -DUSE_SYS_OPENCL=OFF -DETHASHCUDA=ON
ethminer still use ruslo/hunter which is using old download link of boost.
The download link of boost is out of work now. It's the root cause.
Since the ruslo/hunter is not maintained. It's recommended to use https://github.com/cpp-pm/hunter.
The link of boost in cpp-pm/hunter is updated with available link.
The text was updated successfully, but these errors were encountered: