Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Quote
- The quarrel between original Invictus founders became public
link to this quarrel please
yes please, i also want to read this
1963931ms th_a LoginDialog.cpp:57 onLogin ] error unspecified
Unable to create directories channel0/cache_chan_2
{"path":"channel0/cache_chan_2","inner":"Dynamic exception type: N5boost10filesystem16filesystem_errorE\nstd::exception::what: boost::filesystem::create_directories: Permission denied: \"channel0\"\n"}
th_a filesystem.cpp:147 create_directories
{"config":{"data_dir":"/home/eblack/.local/share/KeyhoteeD/profiles/Evan Black/data","network_port":0,"rpc_config":{"port":0,"user":"","pass":""},"enable_upnp":false,"default_nodes":[],"default_mail_nodes":["162.243.67.4:7896"]}}
th_a application.cpp:273 configure
{}
th_a application.cpp:355 load_profile
One quick question, does it matter if I donate from a multi-address PTS/BTC wallet? Or do I have to donate from a single address PTS/BTC wallet? I experienced MMC 2.0 that single address was easy. Please advise.
It should not matter, we will have tools to import all keys from your PTS and BTC wallets.
Thanks for your insight, arcke.
I found this useful post on memory ordering:Quotememory_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.
3333816ms stretch_s keychain.cpp:24 operator() ] stretchign seed
3333816ms stretch_s keychain.cpp:27 operator() ] .
Illegal instruction (core dumped)
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 added this issue on git:
https://github.com/InvictusInnovations/keyhotee/issues/35
https://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_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?
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.
Evan makes a good point, "there is a difference". Your original post is from Dec 5, today I can't even find a quote for Protoshares. The point is there are many ppl that want to be part of this idea but don't have coding abilities. I am new here and trying to add value to an idea that I believe in.
Hayek argued that the goal of Laissez-faire markets is the preservation of the unique information contained in the price itself. Laissez-faire principle expresses a preference for an absence of non-market pressures on prices and wages, such as those from government taxes, subsidies, tariffs, regulation , or government-granted or coercive monopolies.(today) Price and value is determined by the continuous decisions of many people as to what that value is at any given moment.
Where is the market? I want to buy Protoshares and support DAC.
etalon-or
"When you live outside the law, you must be honest."Bob Dylan
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,[/pre]
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
I just successfully compiled it thanks to this thread. Where does it look for wallet.dat and the conf file?
I was browsing CoinMarketCap.com just now and noticed something peculiar. Out of the top ten crypto-currencies, only one has gone up in value over the past 24 hours.
It's nice to be invested in a coin with a price somewhat independent of the price of Bitcoin, but I obviously don't consider ProtoShares just another alt-coin.
You aren't invested in a 'coin'... you are invested in a 'share'.... the other thing that is unique on the list
I am interested in knowing the best practices here... so please help provide suggestions. In particular I want solutions that do not depend upon specialized hardware or centralized services.
