[ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency

[UdjinM6]

I'm trying to build DASH on Mac and getting "not found for architecture x86_64" error when I run make. I pulled DASH repository from git and ran:

Code:

./autogen.sh
./configure
make

Error:

Code:

Undefined symbols for architecture x86_64:
  "boost::this_thread::hiden::sleep_for(timespec const&)", referenced from:
      MilliSleep(long long) in libbitcoin_util.a(libbitcoin_util_a-utiltime.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [dashd] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive] Error 1

Does anybody know what should I do in order for it to work?

Have you installed all the dependencies?
https://github.com/dashpay/dash/blob/master/doc/build-osx.md

I did, I followed that file you posted above.

Hmm... What "brew list boost" shows you? Which version of boost is installed and does it have boost/tread?
e.g. for me it's a bunch of lines one of which is
"/usr/local/Cellar/boost/1.65.1/lib/libboost_thread-mt.dylib"
which means that I have boost 1.65.1 installed and boost/thread lib is indeed a part of that installation.

[1674795067]

1674795067

[1674795067]

1674795067

[1674795067]

1674795067

[lentyna]

I'm trying to build DASH on Mac and getting "not found for architecture x86_64" error when I run make. I pulled DASH repository from git and ran:

Code:

./autogen.sh
./configure
make

Error:

Code:

Undefined symbols for architecture x86_64:
  "boost::this_thread::hiden::sleep_for(timespec const&)", referenced from:
      MilliSleep(long long) in libbitcoin_util.a(libbitcoin_util_a-utiltime.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [dashd] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive] Error 1

Does anybody know what should I do in order for it to work?

Have you installed all the dependencies?
https://github.com/dashpay/dash/blob/master/doc/build-osx.md

I did, I followed that file you posted above.

Hmm... What "brew list boost" shows you? Which version of boost is installed and does it have boost/tread?
e.g. for me it's a bunch of lines one of which is
"/usr/local/Cellar/boost/1.65.1/lib/libboost_thread-mt.dylib"
which means that I have boost 1.65.1 installed and boost/thread lib is indeed a part of that installation.

I have the same:

Code:

brew list boost
/usr/local/Cellar/boost/1.65.1/include/boost/ (12547 files)
/usr/local/Cellar/boost/1.65.1/lib/libboost_atomic-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_chrono-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_chrono.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_container-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_container.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_context-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_coroutine-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_coroutine.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_date_time-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_date_time.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_filesystem-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_filesystem.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_graph-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_graph.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_iostreams-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_iostreams.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_locale-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_log-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_log.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_log_setup-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_log_setup.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_c99-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_c99.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_c99f-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_c99f.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_c99l-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_c99l.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_tr1-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_tr1.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_tr1f-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_tr1f.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_tr1l-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_tr1l.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_prg_exec_monitor-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_prg_exec_monitor.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_program_options-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_program_options.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_random-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_random.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_regex-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_regex.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_serialization-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_serialization.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_signals-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_signals.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_stacktrace_addr2line-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_stacktrace_addr2line.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_stacktrace_basic-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_stacktrace_basic.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_stacktrace_noop-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_stacktrace_noop.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_system-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_system.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_thread-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_timer-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_timer.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_type_erasure-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_type_erasure.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_unit_test_framework-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_unit_test_framework.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_wave-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_wserialization-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_wserialization.dylib
/usr/local/Cellar/boost/1.65.1/lib/ (67 other files)

[qwizzie]

After Bitcoin pump to $11,000 and soon Dump 9,600.
Dash going crazy and pump up 36%.
It's over $600 to the moon.
Are you guys going to replace bitcoin?!

oh darn, they found out about our secret master plan  

[UdjinM6]

I'm trying to build DASH on Mac and getting "not found for architecture x86_64" error when I run make. I pulled DASH repository from git and ran:

Code:

./autogen.sh
./configure
make

Error:

Code:

Undefined symbols for architecture x86_64:
  "boost::this_thread::hiden::sleep_for(timespec const&)", referenced from:
      MilliSleep(long long) in libbitcoin_util.a(libbitcoin_util_a-utiltime.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [dashd] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive] Error 1

Does anybody know what should I do in order for it to work?

Have you installed all the dependencies?
https://github.com/dashpay/dash/blob/master/doc/build-osx.md

I did, I followed that file you posted above.

Hmm... What "brew list boost" shows you? Which version of boost is installed and does it have boost/tread?
e.g. for me it's a bunch of lines one of which is
"/usr/local/Cellar/boost/1.65.1/lib/libboost_thread-mt.dylib"
which means that I have boost 1.65.1 installed and boost/thread lib is indeed a part of that installation.

I have the same:

Code:

brew list boost
/usr/local/Cellar/boost/1.65.1/include/boost/ (12547 files)
/usr/local/Cellar/boost/1.65.1/lib/libboost_atomic-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_chrono-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_chrono.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_container-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_container.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_context-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_coroutine-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_coroutine.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_date_time-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_date_time.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_filesystem-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_filesystem.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_graph-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_graph.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_iostreams-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_iostreams.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_locale-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_log-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_log.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_log_setup-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_log_setup.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_c99-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_c99.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_c99f-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_c99f.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_c99l-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_c99l.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_tr1-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_tr1.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_tr1f-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_tr1f.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_tr1l-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_tr1l.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_prg_exec_monitor-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_prg_exec_monitor.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_program_options-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_program_options.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_random-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_random.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_regex-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_regex.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_serialization-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_serialization.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_signals-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_signals.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_stacktrace_addr2line-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_stacktrace_addr2line.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_stacktrace_basic-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_stacktrace_basic.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_stacktrace_noop-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_stacktrace_noop.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_system-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_system.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_thread-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_timer-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_timer.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_type_erasure-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_type_erasure.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_unit_test_framework-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_unit_test_framework.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_wave-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_wserialization-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_wserialization.dylib
/usr/local/Cellar/boost/1.65.1/lib/ (67 other files)

Ok, this looks good. What about "./configure" output?
Should have these lines:

Code:

checking for boostlib >= 1.20.0... yes
checking whether the Boost::System library is available... yes
checking for exit in -lboost_system... yes
checking whether the Boost::Filesystem library is available... yes
checking for exit in -lboost_filesystem... yes
checking whether the Boost::Program_Options library is available... yes
checking for exit in -lboost_program_options-mt... yes
checking whether the Boost::Thread library is available... yes
checking for exit in -lboost_thread-mt... yes
checking whether the Boost::Chrono library is available... yes
checking for exit in -lboost_chrono-mt... yes
checking whether the Boost::Unit_Test_Framework library is available... yes
checking for dynamic linked boost test... yes

[lentyna]

I'm trying to build DASH on Mac and getting "not found for architecture x86_64" error when I run make. I pulled DASH repository from git and ran:

Code:

./autogen.sh
./configure
make

Error:

Code:

Undefined symbols for architecture x86_64:
  "boost::this_thread::hiden::sleep_for(timespec const&)", referenced from:
      MilliSleep(long long) in libbitcoin_util.a(libbitcoin_util_a-utiltime.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [dashd] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive] Error 1

Does anybody know what should I do in order for it to work?

Have you installed all the dependencies?
https://github.com/dashpay/dash/blob/master/doc/build-osx.md

I did, I followed that file you posted above.

Hmm... What "brew list boost" shows you? Which version of boost is installed and does it have boost/tread?
e.g. for me it's a bunch of lines one of which is
"/usr/local/Cellar/boost/1.65.1/lib/libboost_thread-mt.dylib"
which means that I have boost 1.65.1 installed and boost/thread lib is indeed a part of that installation.

I have the same:

Code:

brew list boost
/usr/local/Cellar/boost/1.65.1/include/boost/ (12547 files)
/usr/local/Cellar/boost/1.65.1/lib/libboost_atomic-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_chrono-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_chrono.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_container-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_container.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_context-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_coroutine-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_coroutine.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_date_time-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_date_time.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_filesystem-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_filesystem.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_graph-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_graph.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_iostreams-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_iostreams.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_locale-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_log-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_log.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_log_setup-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_log_setup.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_c99-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_c99.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_c99f-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_c99f.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_c99l-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_c99l.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_tr1-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_tr1.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_tr1f-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_tr1f.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_tr1l-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_math_tr1l.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_prg_exec_monitor-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_prg_exec_monitor.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_program_options-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_program_options.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_random-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_random.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_regex-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_regex.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_serialization-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_serialization.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_signals-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_signals.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_stacktrace_addr2line-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_stacktrace_addr2line.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_stacktrace_basic-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_stacktrace_basic.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_stacktrace_noop-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_stacktrace_noop.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_system-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_system.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_thread-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_timer-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_timer.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_type_erasure-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_type_erasure.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_unit_test_framework-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_unit_test_framework.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_wave-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_wserialization-mt.dylib
/usr/local/Cellar/boost/1.65.1/lib/libboost_wserialization.dylib
/usr/local/Cellar/boost/1.65.1/lib/ (67 other files)

Ok, this looks good. What about "./configure" output?
Should have these lines:

Code:

checking for boostlib >= 1.20.0... yes
checking whether the Boost::System library is available... yes
checking for exit in -lboost_system... yes
checking whether the Boost::Filesystem library is available... yes
checking for exit in -lboost_filesystem... yes
checking whether the Boost::Program_Options library is available... yes
checking for exit in -lboost_program_options-mt... yes
checking whether the Boost::Thread library is available... yes
checking for exit in -lboost_thread-mt... yes
checking whether the Boost::Chrono library is available... yes
checking for exit in -lboost_chrono-mt... yes
checking whether the Boost::Unit_Test_Framework library is available... yes
checking for dynamic linked boost test... yes

Same as yours:

Code:

checking for boostlib >= 1.20.0... yes
checking whether the Boost::System library is available... yes
checking for exit in -lboost_system... yes
checking whether the Boost::Filesystem library is available... yes
checking for exit in -lboost_filesystem... yes
checking whether the Boost::Program_Options library is available... yes
checking for exit in -lboost_program_options-mt... yes
checking whether the Boost::Thread library is available... yes
checking for exit in -lboost_thread-mt... yes
checking whether the Boost::Chrono library is available... yes
checking for exit in -lboost_chrono-mt... yes
checking whether the Boost::Unit_Test_Framework library is available... yes
checking for dynamic linked boost test... yes
checking for mismatched boost c++11 scoped enums... ok

[lemoon789]

Currently, the bifurcation of the currency market is so hot, DASH plans for bifurcating activities?

[Mangled Blue]

Currently, the bifurcation of the currency market is so hot, DASH plans for bifurcating activities?

DASH does not divide - It conquers

[qwizzie]

This is the only major cryptocurrency afloat in a sea of red
https://www.businessinsider.com.au/cryptocurrency-prices-falling-2017-11

CV Market Watch™: DASH Surprises Again with Move Above $800
https://cryptovest.com/news/cv-market-watch-dash-surprises-again-with-move-above-800/

On the Scaling Debates: How Different Cryptocurrencies Are Tackling Growth
https://blockonomi.com/cryptocurrency-scaling/

[UdjinM6]

I'm trying to build DASH on Mac and getting "not found for architecture x86_64" error when I run make. I pulled DASH repository from git and ran:

Code:

./autogen.sh
./configure
make

Error:

Code:

Undefined symbols for architecture x86_64:
  "boost::this_thread::hiden::sleep_for(timespec const&)", referenced from:
      MilliSleep(long long) in libbitcoin_util.a(libbitcoin_util_a-utiltime.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [dashd] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive] Error 1

Does anybody know what should I do in order for it to work?

... EDIT: all libs  seems to be in place but still no luck....

It's weird then... Try reinstalling boost from scratch and then building it again (but first cleaning all that mess before making new build)

Code:

brew uninstall --force boost
brew install boost
./configure
make clean
make

EDIT: removed over-quoting

[110110101]

Currently, the bifurcation of the currency market is so hot, DASH plans for bifurcating activities?

Dash doesn't need to fork left and right as it has a solid and functioning governance system unlike the Big BTC that must fork to make larger or more fundamental changes to the code base, eg block sizes, add other features etc. With Dash it is the masternode operators who cast their votes and the community reaches consensus on how to proceed forward. The decision to adopt 2 MB blocks was done in about a day for Dash. Bitcoin never came to an agreement on how to proceed, but instead splitt up in a handful of Bitcoin Gold, Bitcoin Cash, Bitcoin $whatever.....

Dash stands stronger together and solves its differences among its stake holders with monthly proposals and voting.

A very valid quote from Mangled Blue:

..

DASH does not divide - It conquers

Dash marches on and focuses forward instead of internal sandbox bickering.

[solowhizkid]

DASH Digital Cash | The Road To $1000 (2MB Block Sizes & Zimbabwe Deal)

https://www.youtube.com/watch?v=q5xfIS7ZMvM

#dash_force

[solowhizkid]

This is the only major cryptocurrency afloat in a sea of red

https://www.businessinsider.com.au/cryptocurrency-prices-falling-2017-11

#dash_force

[MasterMined710]

Dash Force MVP Contest Winners November: Reddit Edition

Once again we will be honoring community members who have been instrumental in helping Dash on Reddit. They spend many hours posting high value comments, fighting trolls and helping new and old community members alike. For that reason we have dedicated the November MVP to them.

Without further ado, this month’s winners are…

solarguy2003

goto1415

Jmmon

FranktBunny

Fount4inhead

Congratulations to all the winners, you will each receive .5 Dash!

Read more: https://www.dashforcenews.com/dash-force-mvp-contest-winners-november-reddit-edition/

With the rise in the Dash price it looks like I will need to lower the MVP prize yet again, these guys have spent countless hours supporting Dash and earned every Duff though. Next month it will be lowered to .25 Dash.

The meetup pricing will also need to be adjusted next month. These are good problems to have!  

[solowhizkid]

Dash Price Continues to Surge - Bitcoin of Privacy Coins?

https://www.youtube.com/watch?v=lZGUX7vy5z0

#dash_force

[Lock$mith]

Dash Price Continues to Surge - Bitcoin of Privacy Coins?

https://www.youtube.com/watch?v=lZGUX7vy5z0

#dash_force

Privacy coins all the way!

[pakhirgan]

Everything is getting crazy!!!!!!!!!!!

[NibiruHybrid]

Dash – What Is The Value Proposition?

With the price increase we have seen in Dash this year, month, week certainly Dash works as a store of value.  We all like to think of Dash as Digital Cash but what strides have been made toward that goal this year?  In this time of crazy price appreciation and multi-million dollar monthly Dash treasury budgets it is good to look at what makes Dash “worth it.”

Read more: https://www.dashforcenews.com/dash-value-proposition/

[Mangled Blue]

Everything is getting crazy!!!!!!!!!!!

"Weak-hands" are being "shook-out"

[popeye95]

After Bitcoin pump to $11,000 and soon Dump 9,600.
Dash going crazy and pump up 36%.
It's over $600 to the moon.
Are you guys going to replace bitcoin?!

Yes, already put my bag in DASH after seeing BTC fall from simple rumor and coinbase problems.

[GrinZ]

It is a fact that Dash will be the next months, we have forgotten Dash because we focus too much on Waves and Ethere as Turks.
Dash mining is being done by a large number of miners, and I was looking at it with certainty, and now it is 1 k in 3 months.