Thanks
I have created a new Digital Ocean - Ubuntu droplet and I am currently following the steps you posted to attempt to recreate the issue - I shall post my findings soon - just kicked off the build
Scanning dependencies of target boost_python
[ 40%] Creating directories for 'boost_python'
[ 40%] No download step for 'boost_python'
[ 40%] No patch step for 'boost_python'
[ 40%] No update step for 'boost_python'
[ 40%] No configure step for 'boost_python'
[ 40%] Performing build step for 'boost_python'
CMake Error at /home/maidsafe/community_python_issue/MaidSafe/build_maidsafe_clang/boost_1_55_0/src/boost_python-stamp/boost_python-build.cmake:16 (message):
Command failed: 1
'/home/maidsafe/community_python_issue/MaidSafe/build_maidsafe_clang/boost_1_55_0_Clang_3_5_0/b2' 'link=static' 'threading=multi' 'runtime-link=shared' '--build-dir=Build' 'stage' '-d+2' '--hash' 'variant=release' 'cxxflags=-fPIC' 'cxxflags=-std=c++11' '-sNO_BZIP2=1' '--layout=tagged' 'toolset=clang-3.5' '--with-python'
See also
/home/maidsafe/community_python_issue/MaidSafe/build_maidsafe_clang/boost_1_55_0/src/boost_python-stamp/boost_python-build-*.log
src/third_party_libs/CMakeFiles/boost_python.dir/build.make:103: recipe for target 'boost_1_55_0/src/boost_python-stamp/boost_python-build' failed
make[2]: *** [boost_1_55_0/src/boost_python-stamp/boost_python-build] Error 1
CMakeFiles/Makefile2:1818: recipe for target 'src/third_party_libs/CMakeFiles/boost_python.dir/all' failed
make[1]: *** [src/third_party_libs/CMakeFiles/boost_python.dir/all] Error 2
Makefile:123: recipe for target 'all' failed
make: *** [all] Error 2
Thank you for reporting this - I shall now create a bug in our JIRA system to get it sorted and I am also now trying to recreate this on a real Ubuntu machine.
Yeah, build is already running with python-dev installed (which was really obvious now that I think about it, but as always, hindsight is 20/20) Will comment on the bug in JIRA as soon as the build finished.
Iām still trying to get LNC running, this time with ubuntu 14.10, error message is still the same, but Iāll try again with clang and Debug.
Can you tell me which OS should work as of now? So far I didnāt have luck with 14.04, 14.10 or arch
I use the LNC routinely on Ubuntu 14.04, most often with clang release. I have some subtle changes different from the next branch, but these address potential errors seemingly different from the ones reported here. Iāll have to do some more tests across different machines and different configurations to get to the bottom of this.
14.10 apparently doesnāt like clang, or in other words I canāt get it working. I guess I have to wait for the installer to be finished because as of now, I canāt get the local_network_controller to start no matter what I try.
EDIT: Damn it, the error is the same, just with more information when cmake is run with debug. Who wouldāve thought
I tried again a couple of days ago and no matter which plattform I use, I canāt get the local_network_controller to start, which is a bit odd, considering that testnet3 supposedly starts in march.
The routing_v2 means we will not need a local network controller, vaults themselves will be self starting. For this reason there is no work on LNC right now, not that it wont reappear though, but now we donāt need it to start networks
Thanks, thatās good to know. So, there is no way to join the current test network? Iām just very curious to see something in action, get a feeling for the performance impacts on the VMs, connection setups, etc.
I am not a patient man and this project is really yanking my chain