BitShares Forum
Main => General Discussion => Topic started by: toast on August 11, 2014, 08:51:18 pm
-
To the moon!
https://www.youtube.com/watch?v=kgHYGw9OL7c
100 BitUSD bounty (on the real chain) if you can cause this:
https://www.youtube.com/watch?v=kAmsi05P9Uw&t=37
That is, finding a bug that causes to have to change the order matching algorithm.
You have to do a fresh checkout from source! Some build configuration stuff changed!
git clone https://github.com/BitShares/bitshares_toolkit.git
cd bitshares_toolkit
git checkout develop
git submodule init
git submodule update
cmake .
make
-
The develop branch again, right?
-
The develop branch again, right?
yes
-
Getting the following. Might just be me but the others compiled without issue.
[ 59%] Built target bts_utilities
Scanning dependencies of target bts_api_generator
[ 60%] Building CXX object libraries/api/CMakeFiles/bts_api_generator.dir/bts_api_generator.cpp.o
make[2]: *** No rule to make target `libraries/leveldb/libleveldb.a', needed by `libraries/api/bts_api_generator'. Stop.
make[1]: *** [libraries/api/CMakeFiles/bts_api_generator.dir/all] Error 2
make: *** [all] Error 2
Did you do a brand new fresh checkout? That's the easiest way
Other way is "rm -r libraries/leveldb && git submodule init && git submodule update" but I'm not sure if it'll work
-
built ok, all the errors I reported last time appear to be fixed (unable to cancel orders, orders being completed without the wallet being updated)! thanks - I can actually test the market now ;)
-
built ok, all the errors I reported last time appear to be fixed (unable to cancel orders, orders being completed without the wallet being updated)! thanks - I can actually test the market now ;)
Awesome! Now I just need to figure out wtf went wrong with my dev environment :).
-
built ok, all the errors I reported last time appear to be fixed (unable to cancel orders, orders being completed without the wallet being updated)! thanks - I can actually test the market now ;)
Awesome! Now I just need to figure out wtf went wrong with my dev environment :).
For now, you may need to go to library/level_db, and do a "make" first, because I have this problem too.
We'll figure it out later, maybe need to update the CMake file.
-
Getting the following. Might just be me but the others compiled without issue.
[ 59%] Built target bts_utilities
Scanning dependencies of target bts_api_generator
[ 60%] Building CXX object libraries/api/CMakeFiles/bts_api_generator.dir/bts_api_generator.cpp.o
make[2]: *** No rule to make target `libraries/leveldb/libleveldb.a', needed by `libraries/api/bts_api_generator'. Stop.
make[1]: *** [libraries/api/CMakeFiles/bts_api_generator.dir/all] Error 2
make: *** [all] Error 2
Did you do a brand new fresh checkout? That's the easiest way
Other way is "rm -r libraries/leveldb && git submodule init && git submodule update" but I'm not sure if it'll work
I had the same problem with fresh checkout. I solved with:
pushd libraries/leveldb/
make
popd
make
-
Thanks spartako! That did the trick. Wonder why it happened this time and not last. Weird.
-
do i need to do "git checkout develop" like run 12?
-
do i need to do "git checkout develop" like run 12?
Yes, I updated OP
-
copy paste my following code to terminal then go for coffee
git clone https://github.com/BitShares/bitshares_toolkit
cd bitshares_toolkit
git checkout develop
git submodule init
git submodule update
cmake .
make
*do i need to do "git checkout develop" like run 12?
Yes, I updated OP
-
Alright, who stirred the Oxygen tanks?
-
100 bitUSD...it seems the dev team is quite confident. A huge wave of testers are approaching...
-
Alright, who stirred the Oxygen tanks?
Something appears to have gone wrong with the leveldb update as we are seeing all kinds of chain issues. Hold off your testing until we are able to course correct and get the chain back on track.
-
100 bitUSD...it seems the dev team is quite confident. A huge wave of testers are approaching...
Hahaha is that sarcasm?
-
Alright, who stirred the Oxygen tanks?
Something appears to have gone wrong with the leveldb update as we are seeing all kinds of chain issues. Hold off your testing until we are able to course correct and get the chain back on track.
https://www.youtube.com/watch?v=kAmsi05P9Uw
-
https://www.youtube.com/watch?v=Zl12dXYcUTo&t=20
watch out for dry run 14...