0 Members and 1 Guest are viewing this topic.
Quote from: drekrob on January 11, 2014, 06:56:38 pmAre 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.
I'm available for graphic design and translating English to Spanish, just in case someone is interested, good quality, fast, economically reasonable...
Is there any guide to build under Ubuntu? I get various compilation errors.
Here is my first attempt for a logo/theme for ProtoShares.. Give me some feedback - http://www.imm.io/1m9hRP.S. I know this is over.. Just doing it for fun!
Quote from: arcke on December 12, 2013, 12:46:34 pmQuote from: Evan on December 11, 2013, 09:58:54 pmThanks for your insight, arcke.I found this useful post on memory ordering:Quote 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.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:Code: [Select]3333816ms stretch_s keychain.cpp:24 operator() ] stretchign seed3333816ms stretch_s keychain.cpp:27 operator() ] .Illegal instruction (core dumped)I tried to compile Keyhotee this morning, and compiling failed with errors:Code: [Select]Generating moc_MailViewer.cppIn 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' failedmake[2]: *** [BitShares/CMakeFiles/bshare.dir/src/network/connection.cpp.o] Error 1CMakeFiles/Makefile2:237: recipe for target 'BitShares/CMakeFiles/bshare.dir/all' failedmake[1]: *** [BitShares/CMakeFiles/bshare.dir/all] Error 2make[1]: *** Waiting for unfinished jobs....I am fairly certain that this commit is to blame.
Quote from: Evan on December 11, 2013, 09:58:54 pmThanks for your insight, arcke.I found this useful post on memory ordering:Quote 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.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:Quote 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.Now Keyhotee crashes after I enter my desired Keyhotee ID, but that's a separate issue.
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.
3333816ms stretch_s keychain.cpp:24 operator() ] stretchign seed3333816ms stretch_s keychain.cpp:27 operator() ] .Illegal instruction (core dumped)
Generating moc_MailViewer.cppIn 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' failedmake[2]: *** [BitShares/CMakeFiles/bshare.dir/src/network/connection.cpp.o] Error 1CMakeFiles/Makefile2:237: recipe for target 'BitShares/CMakeFiles/bshare.dir/all' failedmake[1]: *** [BitShares/CMakeFiles/bshare.dir/all] Error 2make[1]: *** Waiting for unfinished jobs....
Quote from: arcke on December 11, 2013, 02:06:37 pmQuote from: arcke on December 10, 2013, 03:48:11 pmI added this issue on git:https://github.com/InvictusInnovations/keyhotee/issues/35https://github.com/InvictusInnovations/fc/blob/phoenix/src/thread/thread_d.hpp#L221Code: [Select]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.Code: [Select]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_cstI 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:Quote 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.Now Keyhotee crashes after I enter my desired Keyhotee ID, but that's a separate issue.
Quote from: arcke on December 10, 2013, 03:48:11 pmI added this issue on git:https://github.com/InvictusInnovations/keyhotee/issues/35https://github.com/InvictusInnovations/fc/blob/phoenix/src/thread/thread_d.hpp#L221Code: [Select]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.Code: [Select]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_cstI 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
pending = task_in_queue.exchange(0,boost::memory_order_consume);
pending = task_in_queue.exchange(0,boost::memory_order_relaxed);
Quote from: Evan on December 10, 2013, 12:14:35 amQuote from: arcke on December 09, 2013, 03:31:44 pmHave we found a solution to building Keyhotee on Arch Linux with boost library 1.55 installed?Code: [Select]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 revisionPossibly relevant SVN changesetI 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
Quote from: arcke on December 09, 2013, 03:31:44 pmHave we found a solution to building Keyhotee on Arch Linux with boost library 1.55 installed?Code: [Select]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 revisionPossibly relevant SVN changesetI 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?Code: [Select]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]
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
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
Quote from: HackFisher on November 30, 2013, 01:24:12 pmI 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.Quote[ 49%] Building CXX object fc/CMakeFiles/fc.dir/src/thread/thread.cpp.oIn 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.Quote[ 49%] Building CXX object fc/CMakeFiles/fc.dir/src/thread/thread.cpp.oIn 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.
[ 49%] Building CXX object fc/CMakeFiles/fc.dir/src/thread/thread.cpp.oIn 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.
Quote from: bytemaster on November 30, 2013, 02:38:59 pmWhat version of boost?Sent from my iPhone using Tapatalkboost version is 1.54.0 install from source.Sent from my GT-N7100 using Tapatalk
What version of boost?Sent from my iPhone using Tapatalk
Quote from: HackFisher on November 30, 2013, 06:49:18 amHere 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/BitShareshttp://stackoverflow.com/questions/16684533/string-pop-back-function-errorI 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/BitShareshttp://stackoverflow.com/questions/16684533/string-pop-back-function-error
Quote from: HackFisher on November 30, 2013, 02:22:32 amI encoutered another problem, It seems that Cmake cannot detect boost version(boost 1.54.0 installed):Quote-- 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 - donestatusCompiling on UNIXCMake 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 BoostDownload 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):Quote-- 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 - donestatusCompiling on UNIXCMake 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
-- 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 - donestatusCompiling on UNIXCMake 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
/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 1make[1]: *** [CMakeFiles/bshare.dir/all] Error 2make: *** [all] Error 2
...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...
Quote from: bytemaster on November 17, 2013, 07:38:02 pmSeveral 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.
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:Code: [Select][ 19%] Building CXX object bitshares/fc/CMakeFiles/fc.dir/src/thread/thread.cpp.oIn 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));
[ 19%] Building CXX object bitshares/fc/CMakeFiles/fc.dir/src/thread/thread.cpp.oIn 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 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'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?
Quote from: liberman on November 13, 2013, 07:57:24 pmI 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 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.
If you have C++ skills we are looking for talented developers. Please contact me for more info.