BitShares Forum
Main => General Discussion => Topic started by: bytemaster on November 03, 2013, 07:38:10 pm
-
If you have C++ skills we are looking for talented developers. Please contact me for more info.
-
If you have C++ skills we are looking for talented developers. Please contact me for more info.
i'm around
-
I don't know if I am talented, but I know a bit (25 years programming, although not much the last 5). I have time, so perhaps I can help.
-
I don't know if I am talented, but I know a bit (25 years programming, although not much the last 5). I have time, so perhaps I can help.
Anyone interested in helping should get Keyhotee building on your local system. Then I can give you some tasks. If you are able to perform them well you may have a job :)
-
i am not a programmer.
when I was really young I did the research and original high level specification for what became known as the JSON libraries by Douglas Crockford and the rest of the team, so I am code & tech literate but i am much better at this:
technical research
writing documentation
product spec & requirements doc's
use cases, surveying users and customers needs
competitive research and analysis
managing social media, marketing and bizdev teams (if you really want the price to go up)
I also am finishing an MS in industrial economics and innovation management, my focus is on analyzing open source communities.
will work for PTS, if you find any of this useful.
-
I don't know if I am talented, but I know a bit (25 years programming, although not much the last 5). I have time, so perhaps I can help.
Anyone interested in helping should get Keyhotee building on your local system. Then I can give you some tasks. If you are able to perform them well you may have a job :)
Where is the source?
This? https://github.com/InvictusInnovations/keyhotee
-
Yes.
https://github.com/InvictusInnovations
https://github.com/InvictusInnovations/BitShares
https://github.com/InvictusInnovations/keyhotee
https://github.com/InvictusInnovations/fc
git clone Keyhotee
cd keyhotee
git clone bitshares
cd bitshares
git clone fc
cd ..
cd ..
cmake .
make
-
I'm having some problems compiling the sources on Linux (arch). I managed to install a static version of Boost, but I'm getting an error from bitshares/fc/CMakeFiles/fc.dir/src/thread/thread.cpp concerning memory models for "__atomic_exchange".
Where do you talk about this?
-
I'm having some problems compiling the sources on Linux (arch). I managed to install a static version of Boost, but I'm getting an error from bitshares/fc/CMakeFiles/fc.dir/src/thread/thread.cpp concerning memory models for "__atomic_exchange".
Where do you talk about this?
I have compiled it successfully on linux with g++4.7 or newer
I have not seen that particular error. For test machines I simply compiled on DO Ubuntu 13.04 machines.
-
I have some experience with altercoin, and would like to figure out how I could contribute.
I am trying to build the source code and hopefully it could work ASAP.
-
I have some experience with altercoin, and would like to figure out how I could contribute.
I am trying to build the source code and hopefully it could work ASAP.
There are some known bugs with ProtoShares-Qt, particularly on Mac OS X mavericks. Send me a private message when you have the code compiled.
-
I don't know where you do discuss issues, I don't want to fill the thread about them, but here is the error I'm getting:
[ 19%] Building CXX object bitshares/fc/CMakeFiles/fc.dir/src/thread/thread.cpp.o
In file included from /home/javi/opt/src/boost_1_55_0/boost/atomic/detail/platform.hpp:22:0,
from /home/javi/opt/src/boost_1_55_0/boost/atomic/atomic.hpp:17,
from /home/javi/opt/src/boost_1_55_0/boost/atomic.hpp:12,
from /home/javi/opt/src/boost_1_55_0/boost/thread/pthread/once_atomic.hpp:20,
from /home/javi/opt/src/boost_1_55_0/boost/thread/once.hpp:20,
from /home/javi/opt/src/boost_1_55_0/boost/thread.hpp:17,
from /home/javi/opt/src/keyhotee/bitshares/fc/src/thread/thread_d.hpp:4,
from /home/javi/opt/src/keyhotee/bitshares/fc/src/thread/thread.cpp:5:
/home/javi/opt/src/boost_1_55_0/boost/atomic/detail/gcc-atomic.hpp: In member function 'void fc::thread_d::process_tasks()':
/home/javi/opt/src/boost_1_55_0/boost/atomic/detail/gcc-atomic.hpp:1081:95: error: invalid memory model for '__atomic_exchange'
return __atomic_exchange_n(&v_, v, atomics::detail::convert_memory_order_to_gcc(order));
-
I don't know where you do discuss issues, I don't want to fill the thread about them, but here is the error I'm getting:
[ 19%] Building CXX object bitshares/fc/CMakeFiles/fc.dir/src/thread/thread.cpp.o
In file included from /home/javi/opt/src/boost_1_55_0/boost/atomic/detail/platform.hpp:22:0,
from /home/javi/opt/src/boost_1_55_0/boost/atomic/atomic.hpp:17,
from /home/javi/opt/src/boost_1_55_0/boost/atomic.hpp:12,
from /home/javi/opt/src/boost_1_55_0/boost/thread/pthread/once_atomic.hpp:20,
from /home/javi/opt/src/boost_1_55_0/boost/thread/once.hpp:20,
from /home/javi/opt/src/boost_1_55_0/boost/thread.hpp:17,
from /home/javi/opt/src/keyhotee/bitshares/fc/src/thread/thread_d.hpp:4,
from /home/javi/opt/src/keyhotee/bitshares/fc/src/thread/thread.cpp:5:
/home/javi/opt/src/boost_1_55_0/boost/atomic/detail/gcc-atomic.hpp: In member function 'void fc::thread_d::process_tasks()':
/home/javi/opt/src/boost_1_55_0/boost/atomic/detail/gcc-atomic.hpp:1081:95: error: invalid memory model for '__atomic_exchange'
return __atomic_exchange_n(&v_, v, atomics::detail::convert_memory_order_to_gcc(order));
Several other people have been reporting this compile error and yet I have never seen it on any OS (Linux, Mac or Windows). What version of gcc are you using? I compile using gcc-4.8 on OS X and 4.7 on Linux.
-
Several other people have been reporting this compile error and yet I have never seen it on any OS (Linux, Mac or Windows). What version of gcc are you using? I compile using gcc-4.8 on OS X and 4.7 on Linux.
gcc 4.8.2 and boost 1.55 as you can see (it doesn't even start to compile with boost libraries included in my distro Arch).
-
Several other people have been reporting this compile error and yet I have never seen it on any OS (Linux, Mac or Windows). What version of gcc are you using? I compile using gcc-4.8 on OS X and 4.7 on Linux.
gcc 4.8.2 and boost 1.55 as you can see (it doesn't even start to compile with boost libraries included in my distro Arch).
It seems to be a problem with boost. Version 1.54 doesn't compile with newer versions of glibc, and 1.55 has the above problem. The problem with arch is that it usually has the newest version of everything so this things may happen very often.
-
Hi guys!
I would like to give some help here!
I'm software engineer, involve in computer development since 1993, I'm comfortable in C/C++ for all platform!
I strongly believe in Keyhotee, as a data center owner also involve in security question, I always found that Email, are technology from the Past, useful but so old and insecure, at my point of view Email is like an Oil lamp, still working but Electricity is so common sense !! That is my main concern, communicate with people securely is the base of everything!
I've set up the Keyhotee project on my Mac, and ready to dive in that world, but I got some issue to build the project!
Here the error or issue :
.
.
.
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/type_traits:770:38: error:
implicit instantiation of undefined template 'std::__1::hash<fc::ip::endpoint>'
: public integral_constant<bool, __is_empty(_Tp)> {};
.
.
.
.
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/memory:2147:15: error: no matching
constructor for initialization of 'bts::network::connection'
__second_(_VSTD::forward<_Args2>(get<_I2>(__second_args))...)
.
.
.
.
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/memory:2147:15: error: no matching
constructor for initialization of 'bts::network::connection'
__second_(_VSTD::forward<_Args2>(get<_I2>(__second_args))...)
.
..
.
2 warnings and 3 errors generated.
make[2]: *** [bitshares/CMakeFiles/bshare.dir/src/network/server.cpp.o] Error 1
make[1]: *** [bitshares/CMakeFiles/bshare.dir/all] Error 2
I did not search deeply, I believe someone had already found something on that?
Thanks for your help!
Slydee
-
I have not seen that error before. What version of g++?
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
g++ --version give me this:
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1
Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn)
Target: x86_64-apple-darwin13.0.0
Thread model: posix
Thanks!
Slydee
-
Please install macports g++ 4.8
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
Hi bytemaster,
I install it :
g++ --version
g++ (MacPorts gcc48 4.8.2_0) 4.8.2
And select it :
port select --list gcc
Available versions for gcc:
mp-gcc48 (active)
none
But still the same error!
-
I encoutered another problem, It seems that Cmake cannot detect boost version(boost 1.54.0 installed):
-- The C compiler identification is Clang 3.1.0
-- The CXX compiler identification is Clang 3.1.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
statusCompiling on UNIX
CMake Error at /usr/local/Cellar/cmake/2.8.11.2/share/cmake/Modules/FindBoost.cmake:1106 (message):
Unable to find the requested Boost libraries.
Boost version: 1.51.0
Boost include path: /usr/local/include
Detected version of Boost is too old. Requested version was 1.53 (or
newer).
Call Stack (most recent call first):
CMakeLists.txt:62 (FIND_PACKAGE)
-- Could NOT find Boost
-
I encoutered another problem, It seems that Cmake cannot detect boost version(boost 1.54.0 installed):
-- The C compiler identification is Clang 3.1.0
-- The CXX compiler identification is Clang 3.1.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
statusCompiling on UNIX
CMake Error at /usr/local/Cellar/cmake/2.8.11.2/share/cmake/Modules/FindBoost.cmake:1106 (message):
Unable to find the requested Boost libraries.
Boost version: 1.51.0
Boost include path: /usr/local/include
Detected version of Boost is too old. Requested version was 1.53 (or
newer).
Call Stack (most recent call first):
CMakeLists.txt:62 (FIND_PACKAGE)
-- Could NOT find Boost
Download Boost 1.54 and install it from source.
-
I encoutered another problem, It seems that Cmake cannot detect boost version(boost 1.54.0 installed):
-- The C compiler identification is Clang 3.1.0
-- The CXX compiler identification is Clang 3.1.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
statusCompiling on UNIX
CMake Error at /usr/local/Cellar/cmake/2.8.11.2/share/cmake/Modules/FindBoost.cmake:1106 (message):
Unable to find the requested Boost libraries.
Boost version: 1.51.0
Boost include path: /usr/local/include
Detected version of Boost is too old. Requested version was 1.53 (or
newer).
Call Stack (most recent call first):
CMakeLists.txt:62 (FIND_PACKAGE)
-- Could NOT find Boost
Download Boost 1.54 and install it from source.
It works after install it from source, Thanks.
but another error appears, sorry to fullfill this thread with these logs :-\, do anybody know the reason?
/Users/cleney/Temp/keyhotee/BitShares/src/bitname/bitname_hash.cpp: In function 'uint64_t bts::bitname::name_hash(const string&)':
/Users/cleney/Temp/keyhotee/BitShares/src/bitname/bitname_hash.cpp:118:43: error: 'std::string' has no member named 'pop_back'
At global scope:
cc1plus: warning: unrecognized command line option "-Wno-unused-local-typedefs" [enabled by default]
make[2]: *** [CMakeFiles/bshare.dir/src/bitname/bitname_hash.cpp.o] Error 1
make[1]: *** [CMakeFiles/bshare.dir/all] Error 2
make: *** [all] Error 2
I'm wondering if it is caused by some fail when building boost:
...failed darwin.compile.c++ bin.v2/libs/log/build/darwin-4.2.1/release/build-no/link-static/log-api-unix/threading-multi/default_filter_factory.o...
...skipped <pbin.v2/libs/log/build/darwin-4.2.1/release/build-no/link-static/log-api-unix/threading-multi>libboost_log_setup.a(clean) for lack of <pbin.v2/libs/log/build/darwin-4.2.1/release/build-no/link-static/log-api-unix/threading-multi>filter_parser.o...
...skipped <pbin.v2/libs/log/build/darwin-4.2.1/release/build-no/link-static/log-api-unix/threading-multi>libboost_log_setup.a for lack of <pbin.v2/libs/log/build/darwin-4.2.1/release/build-no/link-static/log-api-unix/threading-multi>filter_parser.o...
...skipped <p/usr/local/lib>libboost_log_setup.a for lack of <pbin.v2/libs/log/build/darwin-4.2.1/release/build-no/link-static/log-api-unix/threading-multi>libboost_log_setup.a...
...failed updating 6 targets...
...skipped 4 targets...
-
Here is link says pop_back was introduced in C++11. CPP is not my advantage :) Do we need 4.7 and up, because I'm using g++4.6 according to dependencies on https://github.com/InvictusInnovations/BitShares
http://stackoverflow.com/questions/16684533/string-pop-back-function-error
-
Here is link says pop_back was introduced in C++11. CPP is not my advantage :) Do we need 4.7 and up, because I'm using g++4.6 according to dependencies on https://github.com/InvictusInnovations/BitShares
http://stackoverflow.com/questions/16684533/string-pop-back-function-error
I believe we can modify that particular call as it is the only place it is used. We should aim to support a wider range of compilers.
-
Here is link says pop_back was introduced in C++11. CPP is not my advantage :) Do we need 4.7 and up, because I'm using g++4.6 according to dependencies on https://github.com/InvictusInnovations/BitShares
http://stackoverflow.com/questions/16684533/string-pop-back-function-error
I believe we can modify that particular call as it is the only place it is used. We should aim to support a wider range of compilers.
I changed to g++4.8, and this problem is solved.
Then another error occur, I post it here, if anyone know the reason, please tell me, thanks.
[ 49%] Building CXX object fc/CMakeFiles/fc.dir/src/thread/thread.cpp.o
In file included from /usr/local/include/boost/context/all.hpp:10:0,
from /Users/cleney/Temp/keyhotee/BitShares/fc/src/thread/context.hpp:3,
from /Users/cleney/Temp/keyhotee/BitShares/fc/src/thread/thread_d.hpp:5,
from /Users/cleney/Temp/keyhotee/BitShares/fc/src/thread/thread.cpp:5:
/usr/local/include/boost/context/fcontext.hpp:73:48: warning: 'jump_fcontext' initialized and declared 'extern' [enabled by default]
intptr_t BOOST_CONTEXT_CALLDECL jump_fcontext( fcontext_t * ofc, fcontext_t const* nfc, intptr_t vp, bool preserve_fpu = true);
^
/usr/local/include/boost/context/fcontext.hpp:73:48: error: 'fcontext_t' was not declared in this scope
/usr/local/include/boost/context/fcontext.hpp:73:48: note: suggested alternative:
In file included from /usr/local/include/boost/context/fcontext.hpp:36:0,
from /usr/local/include/boost/context/all.hpp:10,
from /Users/cleney/Temp/keyhotee/BitShares/fc/src/thread/context.hpp:3,
from /Users/cleney/Temp/keyhotee/BitShares/fc/src/thread/thread_d.hpp:5,
from /Users/cleney/Temp/keyhotee/BitShares/fc/src/thread/thread.cpp:5:
/usr/local/include/boost/context/detail/fcontext_x86_64.hpp:45:8: note: 'boost::ctx::fcontext_t'
struct fcontext_t
^
In file included from /usr/local/include/boost/context/all.hpp:10:0,
from /Users/cleney/Temp/keyhotee/BitShares/fc/src/thread/context.hpp:3,
from /Users/cleney/Temp/keyhotee/BitShares/fc/src/thread/thread_d.hpp:5,
from /Users/cleney/Temp/keyhotee/BitShares/fc/src/thread/thread.cpp:5:
/usr/local/include/boost/context/fcontext.hpp:73:61: error: 'ofc' was not declared in this scope
intptr_t BOOST_CONTEXT_CALLDECL jump_fcontext( fcontext_t * ofc, fcontext_t const* nfc, intptr_t vp, bool preserve_fpu = true);
^
/usr/local/include/boost/context/fcontext.hpp:73:66: error: 'fcontext_t' was not declared in this scope
intptr_t BOOST_CONTEXT_CALLDECL jump_fcontext( fcontext_t * ofc, fcontext_t const* nfc, intptr_t vp, bool preserve_fpu = true);
^
compilation terminated due to -fmax-errors=3.
-
What version of boost?
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
What version of boost?
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
boost version is 1.54.0 install from source.
Sent from my GT-N7100 using Tapatalk
-
I am a programmer,and I am always pay attention on this.Perhaps I could help you on this projection.
I am going to set up the Keyhotee project on my Linux.
After a shorter time for examing,I will give the result that I can do it or not.
After all ,I am always working on Linux,I can read out bitcoin- master source.(sorry for my bad in English)
Sent from my iPad using Tapatalk (http://tapatalk.com/m?id=1)
-
What version of boost?
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
boost version is 1.54.0 install from source.
Sent from my GT-N7100 using Tapatalk
Ok, I am back from Thanksgiving with the family and will be able to look into build instructions.
-
I changed to g++4.8, and this problem is solved.
Then another error occur, I post it here, if anyone know the reason, please tell me, thanks.
[ 49%] Building CXX object fc/CMakeFiles/fc.dir/src/thread/thread.cpp.o
In file included from /usr/local/include/boost/context/all.hpp:10:0,
from /Users/cleney/Temp/keyhotee/BitShares/fc/src/thread/context.hpp:3,
from /Users/cleney/Temp/keyhotee/BitShares/fc/src/thread/thread_d.hpp:5,
from /Users/cleney/Temp/keyhotee/BitShares/fc/src/thread/thread.cpp:5:
/usr/local/include/boost/context/fcontext.hpp:73:48: warning: 'jump_fcontext' initialized and declared 'extern' [enabled by default]
intptr_t BOOST_CONTEXT_CALLDECL jump_fcontext( fcontext_t * ofc, fcontext_t const* nfc, intptr_t vp, bool preserve_fpu = true);
^
/usr/local/include/boost/context/fcontext.hpp:73:48: error: 'fcontext_t' was not declared in this scope
/usr/local/include/boost/context/fcontext.hpp:73:48: note: suggested alternative:
In file included from /usr/local/include/boost/context/fcontext.hpp:36:0,
from /usr/local/include/boost/context/all.hpp:10,
from /Users/cleney/Temp/keyhotee/BitShares/fc/src/thread/context.hpp:3,
from /Users/cleney/Temp/keyhotee/BitShares/fc/src/thread/thread_d.hpp:5,
from /Users/cleney/Temp/keyhotee/BitShares/fc/src/thread/thread.cpp:5:
/usr/local/include/boost/context/detail/fcontext_x86_64.hpp:45:8: note: 'boost::ctx::fcontext_t'
struct fcontext_t
^
In file included from /usr/local/include/boost/context/all.hpp:10:0,
from /Users/cleney/Temp/keyhotee/BitShares/fc/src/thread/context.hpp:3,
from /Users/cleney/Temp/keyhotee/BitShares/fc/src/thread/thread_d.hpp:5,
from /Users/cleney/Temp/keyhotee/BitShares/fc/src/thread/thread.cpp:5:
/usr/local/include/boost/context/fcontext.hpp:73:61: error: 'ofc' was not declared in this scope
intptr_t BOOST_CONTEXT_CALLDECL jump_fcontext( fcontext_t * ofc, fcontext_t const* nfc, intptr_t vp, bool preserve_fpu = true);
^
/usr/local/include/boost/context/fcontext.hpp:73:66: error: 'fcontext_t' was not declared in this scope
intptr_t BOOST_CONTEXT_CALLDECL jump_fcontext( fcontext_t * ofc, fcontext_t const* nfc, intptr_t vp, bool preserve_fpu = true);
^
compilation terminated due to -fmax-errors=3.
fcontext_t is defined by boost... can you verify that the boost examples compile?
-
I changed to g++4.8, and this problem is solved.
Then another error occur, I post it here, if anyone know the reason, please tell me, thanks.
[ 49%] Building CXX object fc/CMakeFiles/fc.dir/src/thread/thread.cpp.o
In file included from /usr/local/include/boost/context/all.hpp:10:0,
from /Users/cleney/Temp/keyhotee/BitShares/fc/src/thread/context.hpp:3,
from /Users/cleney/Temp/keyhotee/BitShares/fc/src/thread/thread_d.hpp:5,
from /Users/cleney/Temp/keyhotee/BitShares/fc/src/thread/thread.cpp:5:
/usr/local/include/boost/context/fcontext.hpp:73:48: warning: 'jump_fcontext' initialized and declared 'extern' [enabled by default]
intptr_t BOOST_CONTEXT_CALLDECL jump_fcontext( fcontext_t * ofc, fcontext_t const* nfc, intptr_t vp, bool preserve_fpu = true);
^
/usr/local/include/boost/context/fcontext.hpp:73:48: error: 'fcontext_t' was not declared in this scope
/usr/local/include/boost/context/fcontext.hpp:73:48: note: suggested alternative:
In file included from /usr/local/include/boost/context/fcontext.hpp:36:0,
from /usr/local/include/boost/context/all.hpp:10,
from /Users/cleney/Temp/keyhotee/BitShares/fc/src/thread/context.hpp:3,
from /Users/cleney/Temp/keyhotee/BitShares/fc/src/thread/thread_d.hpp:5,
from /Users/cleney/Temp/keyhotee/BitShares/fc/src/thread/thread.cpp:5:
/usr/local/include/boost/context/detail/fcontext_x86_64.hpp:45:8: note: 'boost::ctx::fcontext_t'
struct fcontext_t
^
In file included from /usr/local/include/boost/context/all.hpp:10:0,
from /Users/cleney/Temp/keyhotee/BitShares/fc/src/thread/context.hpp:3,
from /Users/cleney/Temp/keyhotee/BitShares/fc/src/thread/thread_d.hpp:5,
from /Users/cleney/Temp/keyhotee/BitShares/fc/src/thread/thread.cpp:5:
/usr/local/include/boost/context/fcontext.hpp:73:61: error: 'ofc' was not declared in this scope
intptr_t BOOST_CONTEXT_CALLDECL jump_fcontext( fcontext_t * ofc, fcontext_t const* nfc, intptr_t vp, bool preserve_fpu = true);
^
/usr/local/include/boost/context/fcontext.hpp:73:66: error: 'fcontext_t' was not declared in this scope
intptr_t BOOST_CONTEXT_CALLDECL jump_fcontext( fcontext_t * ofc, fcontext_t const* nfc, intptr_t vp, bool preserve_fpu = true);
^
compilation terminated due to -fmax-errors=3.
fcontext_t is defined by boost... can you verify that the boost examples compile?
ok, I planned to upgrade osx10.7 to 10.9 and Xcode, and re-intall these dependencies, it may take some time.
I'll feedback if its ok or any update.
Thank you so much.
Sent from my GT-N7100 using Tapatalk
-
Wow, you were using an older version.
10.9 has its own issues as I develop on 10.8... namely Apple moved Open GL. I recently got things compiled but had to hack the Qt install and use the 5.2 beta :(
-
Oh,QT5.2!
Sent from my iPad using Tapatalk (http://tapatalk.com/m?id=1)
-
Wow, you were using an older version.
10.9 has its own issues as I develop on 10.8... namely Apple moved Open GL. I recently got things compiled but had to hack the Qt install and use the 5.2 beta :(
I had to create a symbolic link from the old OpenGL header location to the new OpenGL header location.
-
How many developers do you have on this, just out of interest.
Wish i could help but my skills are not in this area.
-
6-7
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
Have we found a solution to building Keyhotee on Arch Linux with boost library 1.55 installed?
In file included from /usr/include/boost/atomic/detail/platform.hpp:22:0,
from /usr/include/boost/atomic/atomic.hpp:17,
from /usr/include/boost/atomic.hpp:12,
from /usr/include/boost/thread/pthread/once_atomic.hpp:20,
from /usr/include/boost/thread/once.hpp:20,
from /usr/include/boost/thread.hpp:17,
from /home/arcke/src/keyhotee/BitShares/fc/src/thread/thread_d.hpp:4,
from /home/arcke/src/keyhotee/BitShares/fc/src/thread/thread.cpp:5:
/usr/include/boost/atomic/detail/gcc-atomic.hpp: In member function ‘void fc::thread_d::process_tasks()’:
/usr/include/boost/atomic/detail/gcc-atomic.hpp:1081:95: error: invalid memory model for ‘__atomic_exchange’
return __atomic_exchange_n(&v_, v, atomics::detail::convert_memory_order_to_gcc(order));
^
BitShares/fc/CMakeFiles/fc.dir/build.make:149: recipe for target 'BitShares/fc/CMakeFiles/fc.dir/src/thread/thread.cpp.o' failed
[/pre]
-
Have we found a solution to building Keyhotee on Arch Linux with boost library 1.55 installed?
In file included from /usr/include/boost/atomic/detail/platform.hpp:22:0,
from /usr/include/boost/atomic/atomic.hpp:17,
from /usr/include/boost/atomic.hpp:12,
from /usr/include/boost/thread/pthread/once_atomic.hpp:20,
from /usr/include/boost/thread/once.hpp:20,
from /usr/include/boost/thread.hpp:17,
from /home/arcke/src/keyhotee/BitShares/fc/src/thread/thread_d.hpp:4,
from /home/arcke/src/keyhotee/BitShares/fc/src/thread/thread.cpp:5:
/usr/include/boost/atomic/detail/gcc-atomic.hpp: In member function ‘void fc::thread_d::process_tasks()’:
/usr/include/boost/atomic/detail/gcc-atomic.hpp:1081:95: error: invalid memory model for ‘__atomic_exchange’
return __atomic_exchange_n(&v_, v, atomics::detail::convert_memory_order_to_gcc(order));
^
BitShares/fc/CMakeFiles/fc.dir/build.make:149: recipe for target 'BitShares/fc/CMakeFiles/fc.dir/src/thread/thread.cpp.o' failed
[/pre]
I wish I had a solution since I have also unsuccessfully tried to compile Keyhotee with boost 1.55 on Arch Linux.
Based on my research (or the best I can do as a non-coder), the file boost/atomic/detail/platform.hpp in boost 1.55 includes a file, boost/atomic/detail/gcc-atomic.hpp, that does not exist in boost 1.54.
Possibly relevant Git revision (https://github.com/boostorg/atomic/commit/822d7655cfb533e1716ceb157ce95ba2a5c113e2#diff-c2ccfeb733c2452f2d782c2b343b6628)
Possibly relevant SVN changeset (https://svn.boost.org/trac/boost/changeset/85092)
I am hopeful that this will be resolved by the time that Keyhotee goes live New Year's Eve since having a Keyhotee Founder ID is not particularly useful to me if I cannot simply compile and run Keyhotee on my preferred OS.
-
Have we found a solution to building Keyhotee on Arch Linux with boost library 1.55 installed?
In file included from /usr/include/boost/atomic/detail/platform.hpp:22:0,
from /usr/include/boost/atomic/atomic.hpp:17,
from /usr/include/boost/atomic.hpp:12,
from /usr/include/boost/thread/pthread/once_atomic.hpp:20,
from /usr/include/boost/thread/once.hpp:20,
from /usr/include/boost/thread.hpp:17,
from /home/arcke/src/keyhotee/BitShares/fc/src/thread/thread_d.hpp:4,
from /home/arcke/src/keyhotee/BitShares/fc/src/thread/thread.cpp:5:
/usr/include/boost/atomic/detail/gcc-atomic.hpp: In member function ‘void fc::thread_d::process_tasks()’:
/usr/include/boost/atomic/detail/gcc-atomic.hpp:1081:95: error: invalid memory model for ‘__atomic_exchange’
return __atomic_exchange_n(&v_, v, atomics::detail::convert_memory_order_to_gcc(order));
^
BitShares/fc/CMakeFiles/fc.dir/build.make:149: recipe for target 'BitShares/fc/CMakeFiles/fc.dir/src/thread/thread.cpp.o' failed
[/pre]
I wish I had a solution since I have also unsuccessfully tried to compile Keyhotee with boost 1.55 on Arch Linux.
Based on my research (or the best I can do as a non-coder), the file boost/atomic/detail/platform.hpp in boost 1.55 includes a file, boost/atomic/detail/gcc-atomic.hpp, that does not exist in boost 1.54.
Possibly relevant Git revision (https://github.com/boostorg/atomic/commit/822d7655cfb533e1716ceb157ce95ba2a5c113e2#diff-c2ccfeb733c2452f2d782c2b343b6628)
Possibly relevant SVN changeset (https://svn.boost.org/trac/boost/changeset/85092)
I am hopeful that this will be resolved by the time that Keyhotee goes live New Year's Eve since having a Keyhotee Founder ID is not particularly useful to me if I cannot simply compile and run Keyhotee on my preferred OS.
I added this issue on git:
https://github.com/InvictusInnovations/keyhotee/issues/35
-
Have we found a solution to building Keyhotee on Arch Linux with boost library 1.55 installed?
In file included from /usr/include/boost/atomic/detail/platform.hpp:22:0,
from /usr/include/boost/atomic/atomic.hpp:17,
from /usr/include/boost/atomic.hpp:12,
from /usr/include/boost/thread/pthread/once_atomic.hpp:20,
from /usr/include/boost/thread/once.hpp:20,
from /usr/include/boost/thread.hpp:17,
from /home/arcke/src/keyhotee/BitShares/fc/src/thread/thread_d.hpp:4,
from /home/arcke/src/keyhotee/BitShares/fc/src/thread/thread.cpp:5:
/usr/include/boost/atomic/detail/gcc-atomic.hpp: In member function ‘void fc::thread_d::process_tasks()’:
/usr/include/boost/atomic/detail/gcc-atomic.hpp:1081:95: error: invalid memory model for ‘__atomic_exchange’
return __atomic_exchange_n(&v_, v, atomics::detail::convert_memory_order_to_gcc(order));
^
BitShares/fc/CMakeFiles/fc.dir/build.make:149: recipe for target 'BitShares/fc/CMakeFiles/fc.dir/src/thread/thread.cpp.o' failed
[/pre]
I wish I had a solution since I have also unsuccessfully tried to compile Keyhotee with boost 1.55 on Arch Linux.
Based on my research (or the best I can do as a non-coder), the file boost/atomic/detail/platform.hpp in boost 1.55 includes a file, boost/atomic/detail/gcc-atomic.hpp, that does not exist in boost 1.54.
Possibly relevant Git revision (https://github.com/boostorg/atomic/commit/822d7655cfb533e1716ceb157ce95ba2a5c113e2#diff-c2ccfeb733c2452f2d782c2b343b6628)
Possibly relevant SVN changeset (https://svn.boost.org/trac/boost/changeset/85092)
I am hopeful that this will be resolved by the time that Keyhotee goes live New Year's Eve since having a Keyhotee Founder ID is not particularly useful to me if I cannot simply compile and run Keyhotee on my preferred OS.
I added this issue on git:
https://github.com/InvictusInnovations/keyhotee/issues/35
https://github.com/InvictusInnovations/fc/blob/phoenix/src/thread/thread_d.hpp#L221
pending = task_in_queue.exchange(0,boost::memory_order_consume);
Changing the used memory order in this call to exchange to any of the other memory orderings fixes compilation.
pending = task_in_queue.exchange(0,boost::memory_order_relaxed);
Choose any of:
memory_order_relaxed
memory_order_acquire
memory_order_release
memory_order_acq_rel
memory_order_seq_cst
I am not sure if this is correct. I was still not able to install keyhotee into the system root. How to do an install to $HOME?
-
I added this issue on git:
https://github.com/InvictusInnovations/keyhotee/issues/35
https://github.com/InvictusInnovations/fc/blob/phoenix/src/thread/thread_d.hpp#L221
pending = task_in_queue.exchange(0,boost::memory_order_consume);
Changing the used memory order in this call to exchange to any of the other memory orderings fixes compilation.
pending = task_in_queue.exchange(0,boost::memory_order_relaxed);
Choose any of:
memory_order_relaxed
memory_order_acquire
memory_order_release
memory_order_acq_rel
memory_order_seq_cst
I am not sure if this is correct. I was still not able to install keyhotee into the system root. How to do an install to $HOME?
Thanks for your insight, arcke.
I found this useful post on memory ordering (http://bartoszmilewski.com/2008/12/01/c-atomics-and-memory-ordering/):
memory_order_acquire: guarantees that subsequent loads are not moved before the current load or any preceding loads.
memory_order_release: preceding stores are not moved past the current store or any subsequent stores.
memory_order_acq_rel: combines the two previous guarantees.
memory_order_consume: potentially weaker form of memory_order_acquire that enforces ordering of the current load before other operations that are data-dependent on it (for instance, when a load of a pointer is marked memory_order_consume, subsequent operations that dereference this pointer won’t be moved before it (yes, even that is not guaranteed on all platforms!).
memory_order_relaxed: all reorderings are okay.
Based on this, I decided to go with memory_order_acquire. After changing the memory order model, I successfully compiled Keyhotee with Boost 1.55 on Arch Linux.
For installing Keyhotee, you can check out my current working PKGBUILD (http://pastebin.com/578GbHcx).
Now Keyhotee crashes after I enter my desired Keyhotee ID, but that's a separate issue.
-
I added this issue on git:
https://github.com/InvictusInnovations/keyhotee/issues/35
https://github.com/InvictusInnovations/fc/blob/phoenix/src/thread/thread_d.hpp#L221
pending = task_in_queue.exchange(0,boost::memory_order_consume);
Changing the used memory order in this call to exchange to any of the other memory orderings fixes compilation.
pending = task_in_queue.exchange(0,boost::memory_order_relaxed);
Choose any of:
memory_order_relaxed
memory_order_acquire
memory_order_release
memory_order_acq_rel
memory_order_seq_cst
I am not sure if this is correct. I was still not able to install keyhotee into the system root. How to do an install to $HOME?
Thanks for your insight, arcke.
I found this useful post on memory ordering (http://bartoszmilewski.com/2008/12/01/c-atomics-and-memory-ordering/):
memory_order_acquire: guarantees that subsequent loads are not moved before the current load or any preceding loads.
memory_order_release: preceding stores are not moved past the current store or any subsequent stores.
memory_order_acq_rel: combines the two previous guarantees.
memory_order_consume: potentially weaker form of memory_order_acquire that enforces ordering of the current load before other operations that are data-dependent on it (for instance, when a load of a pointer is marked memory_order_consume, subsequent operations that dereference this pointer won’t be moved before it (yes, even that is not guaranteed on all platforms!).
memory_order_relaxed: all reorderings are okay.
Based on this, I decided to go with memory_order_acquire. After changing the memory order model, I successfully compiled Keyhotee with Boost 1.55 on Arch Linux.
For installing Keyhotee, you can check out my current working PKGBUILD (http://pastebin.com/578GbHcx).
Now Keyhotee crashes after I enter my desired Keyhotee ID, but that's a separate issue.
I managed to find out how to tell cmake to install to $HOME, and I am having the same issue you are saying. Is this a new issue or are you referring to an issue already reported on git. I cant seem to find it.
-
Thanks for your insight, arcke.
I found this useful post on memory ordering (http://bartoszmilewski.com/2008/12/01/c-atomics-and-memory-ordering/):
memory_order_acquire: guarantees that subsequent loads are not moved before the current load or any preceding loads.
memory_order_release: preceding stores are not moved past the current store or any subsequent stores.
memory_order_acq_rel: combines the two previous guarantees.
memory_order_consume: potentially weaker form of memory_order_acquire that enforces ordering of the current load before other operations that are data-dependent on it (for instance, when a load of a pointer is marked memory_order_consume, subsequent operations that dereference this pointer won’t be moved before it (yes, even that is not guaranteed on all platforms!).
memory_order_relaxed: all reorderings are okay.
Based on this, I decided to go with memory_order_acquire. After changing the memory order model, I successfully compiled Keyhotee with Boost 1.55 on Arch Linux.
For installing Keyhotee, you can check out my current working PKGBUILD (http://pastebin.com/578GbHcx).
Now Keyhotee crashes after I enter my desired Keyhotee ID, but that's a separate issue.
I managed to find out how to tell cmake to install to $HOME, and I am having the same issue you are saying. Is this a new issue or are you referring to an issue already reported on git. I cant seem to find it.
Ah, I was not clear. I have not yet reported this issue on git. I am preparing to be away from my keyboard 12/14-12/21, so I will be unavailable to test any possible solutions for a while. If you could report it in the mean time, I would greatly appreciate it.
The console log reports this after crashing upon clicking "Finish" on the Create Keyhotee ID dialog box:
3333816ms stretch_s keychain.cpp:24 operator() ] stretchign seed
3333816ms stretch_s keychain.cpp:27 operator() ] .
Illegal instruction (core dumped)
I tried to compile Keyhotee this morning, and compiling failed with errors:
Generating moc_MailViewer.cpp
In file included from /home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/src/network/connection.cpp:8:0:
/home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/fc/include/fc/thread/thread.hpp: In instantiation of ‘fc::future<decltype (f())> fc::async(Functor&&, const char*, fc::priority) [with Functor = bts::network::connection::connection(const stcp_socket_ptr&, bts::network::connection_delegate*)::__lambda0; decltype (f()) = void]’:
/home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/src/network/connection.cpp:127:67: required from here
/home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/fc/include/fc/thread/thread.hpp:176:79: error: use of deleted function ‘fc::future<void>::future(const fc::future<void>&)’
return fc::thread::current().async( fc::forward<Functor>(f), desc, prio );
^
In file included from /home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/fc/include/fc/thread/task.hpp:2:0,
from /home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/fc/include/fc/thread/thread.hpp:2,
from /home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/src/network/connection.cpp:8:
/home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/fc/include/fc/thread/future.hpp:224:9: note: ‘fc::future<void>::future(const fc::future<void>&)’ is implicitly declared as deleted because ‘fc::future<void>’ declares a move constructor or move assignment operator
class future<void> {
^
In file included from /home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/src/network/connection.cpp:8:0:
/home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/fc/include/fc/thread/thread.hpp: In instantiation of ‘fc::future<decltype (f())> fc::async(Functor&&, const char*, fc::priority) [with Functor = bts::network::connection::connect(const fc::ip::endpoint&)::__lambda1; decltype (f()) = void]’:
/home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/src/network/connection.cpp:187:70: required from here
/home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/fc/include/fc/thread/thread.hpp:176:79: error: use of deleted function ‘fc::future<void>::future(const fc::future<void>&)’
return fc::thread::current().async( fc::forward<Functor>(f), desc, prio );
^
In file included from /home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/src/network/connection.cpp:8:0:
/home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/fc/include/fc/thread/thread.hpp: In instantiation of ‘fc::future<decltype (f())> fc::thread::async(Functor&&, const char*, fc::priority) [with Functor = bts::network::connection::connection(const stcp_socket_ptr&, bts::network::connection_delegate*)::__lambda0; decltype (f()) = void]’:
/home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/fc/include/fc/thread/thread.hpp:176:79: required from ‘fc::future<decltype (f())> fc::async(Functor&&, const char*, fc::priority) [with Functor = bts::network::connection::connection(const stcp_socket_ptr&, bts::network::connection_delegate*)::__lambda0; decltype (f()) = void]’
/home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/src/network/connection.cpp:127:67: required from here
/home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/fc/include/fc/thread/thread.hpp:62:17: error: use of deleted function ‘fc::future<void>::future(const fc::future<void>&)’
return r;
^
compilation terminated due to -fmax-errors=3.
BitShares/CMakeFiles/bshare.dir/build.make:103: recipe for target 'BitShares/CMakeFiles/bshare.dir/src/network/connection.cpp.o' failed
make[2]: *** [BitShares/CMakeFiles/bshare.dir/src/network/connection.cpp.o] Error 1
CMakeFiles/Makefile2:237: recipe for target 'BitShares/CMakeFiles/bshare.dir/all' failed
make[1]: *** [BitShares/CMakeFiles/bshare.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
I am fairly certain that this commit (https://github.com/InvictusInnovations/fc/commit/8e47816c4ebc4ef1cbcbea60139c2795a73871e5) is to blame.
-
Thanks for your insight, arcke.
I found this useful post on memory ordering (http://bartoszmilewski.com/2008/12/01/c-atomics-and-memory-ordering/):
memory_order_acquire: guarantees that subsequent loads are not moved before the current load or any preceding loads.
memory_order_release: preceding stores are not moved past the current store or any subsequent stores.
memory_order_acq_rel: combines the two previous guarantees.
memory_order_consume: potentially weaker form of memory_order_acquire that enforces ordering of the current load before other operations that are data-dependent on it (for instance, when a load of a pointer is marked memory_order_consume, subsequent operations that dereference this pointer won’t be moved before it (yes, even that is not guaranteed on all platforms!).
memory_order_relaxed: all reorderings are okay.
Based on this, I decided to go with memory_order_acquire. After changing the memory order model, I successfully compiled Keyhotee with Boost 1.55 on Arch Linux.
For installing Keyhotee, you can check out my current working PKGBUILD (http://pastebin.com/578GbHcx).
Now Keyhotee crashes after I enter my desired Keyhotee ID, but that's a separate issue.
I managed to find out how to tell cmake to install to $HOME, and I am having the same issue you are saying. Is this a new issue or are you referring to an issue already reported on git. I cant seem to find it.
Ah, I was not clear. I have not yet reported this issue on git. I am preparing to be away from my keyboard 12/14-12/21, so I will be unavailable to test any possible solutions for a while. If you could report it in the mean time, I would greatly appreciate it.
The console log reports this after crashing upon clicking "Finish" on the Create Keyhotee ID dialog box:
3333816ms stretch_s keychain.cpp:24 operator() ] stretchign seed
3333816ms stretch_s keychain.cpp:27 operator() ] .
Illegal instruction (core dumped)
I tried to compile Keyhotee this morning, and compiling failed with errors:
Generating moc_MailViewer.cpp
In file included from /home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/src/network/connection.cpp:8:0:
/home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/fc/include/fc/thread/thread.hpp: In instantiation of ‘fc::future<decltype (f())> fc::async(Functor&&, const char*, fc::priority) [with Functor = bts::network::connection::connection(const stcp_socket_ptr&, bts::network::connection_delegate*)::__lambda0; decltype (f()) = void]’:
/home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/src/network/connection.cpp:127:67: required from here
/home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/fc/include/fc/thread/thread.hpp:176:79: error: use of deleted function ‘fc::future<void>::future(const fc::future<void>&)’
return fc::thread::current().async( fc::forward<Functor>(f), desc, prio );
^
In file included from /home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/fc/include/fc/thread/task.hpp:2:0,
from /home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/fc/include/fc/thread/thread.hpp:2,
from /home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/src/network/connection.cpp:8:
/home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/fc/include/fc/thread/future.hpp:224:9: note: ‘fc::future<void>::future(const fc::future<void>&)’ is implicitly declared as deleted because ‘fc::future<void>’ declares a move constructor or move assignment operator
class future<void> {
^
In file included from /home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/src/network/connection.cpp:8:0:
/home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/fc/include/fc/thread/thread.hpp: In instantiation of ‘fc::future<decltype (f())> fc::async(Functor&&, const char*, fc::priority) [with Functor = bts::network::connection::connect(const fc::ip::endpoint&)::__lambda1; decltype (f()) = void]’:
/home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/src/network/connection.cpp:187:70: required from here
/home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/fc/include/fc/thread/thread.hpp:176:79: error: use of deleted function ‘fc::future<void>::future(const fc::future<void>&)’
return fc::thread::current().async( fc::forward<Functor>(f), desc, prio );
^
In file included from /home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/src/network/connection.cpp:8:0:
/home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/fc/include/fc/thread/thread.hpp: In instantiation of ‘fc::future<decltype (f())> fc::thread::async(Functor&&, const char*, fc::priority) [with Functor = bts::network::connection::connection(const stcp_socket_ptr&, bts::network::connection_delegate*)::__lambda0; decltype (f()) = void]’:
/home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/fc/include/fc/thread/thread.hpp:176:79: required from ‘fc::future<decltype (f())> fc::async(Functor&&, const char*, fc::priority) [with Functor = bts::network::connection::connection(const stcp_socket_ptr&, bts::network::connection_delegate*)::__lambda0; decltype (f()) = void]’
/home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/src/network/connection.cpp:127:67: required from here
/home/eblack/tempfiles/keyhotee/src/keyhotee/BitShares/fc/include/fc/thread/thread.hpp:62:17: error: use of deleted function ‘fc::future<void>::future(const fc::future<void>&)’
return r;
^
compilation terminated due to -fmax-errors=3.
BitShares/CMakeFiles/bshare.dir/build.make:103: recipe for target 'BitShares/CMakeFiles/bshare.dir/src/network/connection.cpp.o' failed
make[2]: *** [BitShares/CMakeFiles/bshare.dir/src/network/connection.cpp.o] Error 1
CMakeFiles/Makefile2:237: recipe for target 'BitShares/CMakeFiles/bshare.dir/all' failed
make[1]: *** [BitShares/CMakeFiles/bshare.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
I am fairly certain that this commit (https://github.com/InvictusInnovations/fc/commit/8e47816c4ebc4ef1cbcbea60139c2795a73871e5) is to blame.
I get the same error. The pulled changes to thread_d.hpp are correct, however the work done in future.hpp is responsible for breaking the build.
-
Here is my first attempt for a logo/theme for ProtoShares.. Give me some feedback - http://www.imm.io/1m9hR
P.S. I know this is over.. Just doing it for fun!
-
I Here to help and I have many people looking for work even volunteers lets take back our
System from the Elites One Day At a Time!
-
Here is my first attempt for a logo/theme for ProtoShares.. Give me some feedback - http://www.imm.io/1m9hR
P.S. I know this is over.. Just doing it for fun!
What's over? Clueless here :)
I like it. I might discard the ribbon, and maybe make the whole thing look more coin-ish. Maybe with a font that could be minted on to a coin (a more slab or slab-serif font)? OR dramatically depart from that theme, and make it look like non-denominational universal fiat paper (whatever that looks like) and/or company shares.
BTW (@forum/bytemaster), I'm curious:
1) What libraries/tools are required to build Keyhotee on Windows 7, e.g. what version of QT, boost, etc. Going to try to give it a spin.
2) Is/will the development version (and/or the beta) be on a testnet?
-
Hi, maybe you could offer permanent jobs to those who jump onto Bounties (like me) it simplifies things and halts delays caused by the need for someone with permissions to review code. Employees get access right?
-
Is there any guide to build under Ubuntu? I get various compilation errors.
-
Is there any guide to build under Ubuntu? I get various compilation errors.
https://bitsharestalk.org/index.php?topic=1672.msg19078#msg19078
What are you doing now to build it and what errors are you getting? Let me know where you get stuck.
-
I'm available for graphic design and translating English to Spanish, just in case someone is interested, good quality, fast, economically reasonable...
-
I'm available for graphic design and translating English to Spanish, just in case someone is interested, good quality, fast, economically reasonable...
We need a lot of graphic design work and translation into Spanish. Let your skills be known in the Website Bounty Thread and I believe there is a $12K sub-bounty for website logos.
-
Are you still looking for c++ coding? I already wrote you in keyhotee but i'm not sure if you got the message.
-
Are you still looking for c++ coding? I already wrote you in keyhotee but i'm not sure if you got the message.
We are looking to hire quality c++ developers full time. AGS funding has opened up many positions, please email me dlarimer at invictus-innovations....
-
Are you still looking for c++ coding? I already wrote you in keyhotee but i'm not sure if you got the message.
We are looking to hire quality c++ developers full time. AGS funding has opened up many positions, please email me dlarimer at invictus-innovations....
If you (invictus) were here 10 years ago... I would have jumped in to apply with a "I don't care for the salary"...