Something has changed.
Boost now compiles something with equihash in it.
At least it tries to.
I set up a new Ubuntu.
I ran into the same issues again and they were not related to playing around with libboost.
Along the way, I found out more about my hardware:
While I couldn't manage to make Ubuntu accept the onboard graphics as primary display driver ( I thought that might give me more hashes with the PCI card ), I found the options to deactivate onboard HDMI sound and also to reduce shared memory for the onboard graphics.
With a different mainboard, I could turn off the onboard graphics completely and unlock my i3 6300 from 3.8 GHz to 4.x ..
I didn't realise that, when I bought it.
Fresh Ubuntu, same issues
At least I now know it wasn't because of that.
My Ubuntu installation was just as unoperational as this fresh one is.
The only cmake command that allows me to set boost up for compilation is this:
cmake -DCMAKE_BUILD_TYPE=Release -DENABLE_CONTENT_PATCHING=OFF -DLOW_MEMORY_NODE=ON -D_boost_TEST_VERSIONS=1.57 -DBoost_DEBUG=ON -DCMAKE_C_COMPILER=gcc -DCMAKE_CXX_COMPILER=gcc
That I have to specifically place gcc into the arguments is neccessary ( Don't ask me why, please ).
make
It doesn't go very far, then:
A quick check of steemdb.com:
Yep, they are mining away happily.
I'm confused with versions now.
Am I trying to compile the latest github release ( 0.16 ) ?
Witnesses run 0.15
I'm also confused, which fork went through, or was delayed.
Changes are communicated there:
@steemitblog/final-review-of-steem-economic-changes
No indications for a version number.
Personally, I would label the proposed version 0.2 or Beta 2.0
The changes are quite substantial in my opinion.
It seems, that for further progress I will have to join github.
I will do the tutorial and write a 'hello git', or whatever it takes.
For now I'm frustrated.
Could we please communicate this stuff on the frontend as well ?
Initially, I was just trying to build a curation bot.
It was no surprise to me, that I had to dig a little deeper to get to where I want, but this is getting out of hand :D
I'm glad I got votes for this series of posts, but I would appreciate some help, too.
The latest miner guides are months old and the story basically ended with finished binaries available for Windows.
I'm happy about equihash, from what I understand.
The computations are very simple, but they require 128 MB of ram accessed in a manner that should saturate the memory bus.
( source: @steemitblog )
I assume that is to prevent GPU mining ?
Interesting times ahead, I wish I knew what's going on :)