0.16 wallet and bounty news??

[IGJ]

Yes transactions from 16.3 are broadcasted to 10.2 , but they are rejected. Found the reason why - version of the transaction. 10.2 checks if transaction version is bigger or lower than 1 and reject to add it to mempool + generating this error in the logs:
2018-10-09 11:23:12 ERROR: AcceptToMemoryPool : nonstandard transaction: version
16.3 set transaction version = 2 .
I am not familiar what tx version do (maybe clo1 could explain) but start experimenting and created another one transaction in 16.3 with version = 1. It is still not appear in 10.2 nodes, but I am not sure if it is stuck because the first stucked transaction which is in my 16.3 mempool or there is other reason. I will wait you to mine one more block with 16.3 and then we will see.

I see your transaction 0db9d7dc617c85f4150831253e020dfc692c91c9e28c4b1a2141209f1c1348a4 in my 16.3 mempool so I guess T adresses are broadcasted ok between 16.3 nodes.

What do you see in your 16.3 mempool ( riecon-cli getrawmempool ) ?

EDIT:
Ok you mined one block, and both my stuck transactions gone. After that I put another transaction with changed version number from 2 (default in 16.3) to 1 (10.2 accept only 1) and it was broadcasted and appeared in 10.2 mempool. So the problem is transaction version, clo1 maybe have to explain what can go wrong if we change transaction version. Another one important observation from these tests are that if you have one stuck transaction all other transactions created from the same 16.3 wallet, after that will stuck too when broadcasted to 10.2.

[Pttn]

Great, I am glad that this transaction involving a "T" address went through :D !

Now, I cannot spend what I sent to this address, the Debug.log says "CommitTransaction(): Transaction cannot be broadcast immediately, no-witness-yet", so the wallet is not willing to broadcast it. I think that now, it is the clo1's or some other Core specialist's turn to intervene.

I will also let the specialists talk about the transaction version, although there should be plenty of documentation about this in the web.

[IGJ]

When i execute the last make command i get the following output
....

user@Laptop:/usr/src/riecoin$ make
cd . && /bin/bash ./config.status Makefile
config.status: creating Makefile
Making all in src
make[1]: Entering directory '/usr/src/riecoin/src'
cd .. && /bin/bash ./config.status src/Makefile depfiles
config.status: creating src/Makefile
config.status: executing depfiles commands
make[2]: Entering directory '/usr/src/riecoin/src'
make[3]: Entering directory '/usr/src/riecoin'
make[3]: Leaving directory '/usr/src/riecoin'
CXX riecoind-bitcoind.o
In file included from ./util.h:19:0,
from bitcoind.cpp:17:
./sync.h:94:53: error: ‘recursive_mutex’ is not a member of ‘std’
class CCriticalSection : public AnnotatedMixin<std::recursive_mutex>
^~~~~~~~~~~~~~~
./sync.h:94:53: error: ‘recursive_mutex’ is not a member of ‘std’
./sync.h:94:68: error: template argument 1 is invalid
class CCriticalSection : public AnnotatedMixin<std::recursive_mutex>
^
./sync.h:103:29: error: ‘mutex’ is not a member of ‘std’
typedef AnnotatedMixin<std::mutex> CWaitableCriticalSection;
^~~~~
./sync.h:103:29: error: ‘mutex’ is not a member of ‘std’
./sync.h:103:34: error: template argument 1 is invalid
typedef AnnotatedMixin<std::mutex> CWaitableCriticalSection;
^
./sync.h:106:14: error: ‘condition_variable’ in namespace ‘std’ does not name a type
typedef std::condition_variable CConditionVariable;
^~~~~~~~~~~~~~~~~~
./sync.h:109:31: error: ‘mutex’ is not a member of ‘std’
typedef std::unique_lock<std::mutex> WaitableLock;
^~~~~
./sync.h:109:31: error: ‘mutex’ is not a member of ‘std’
./sync.h:109:36: error: template argument 1 is invalid
typedef std::unique_lock<std::mutex> WaitableLock;
^
In file included from ./util.h:19:0,
from bitcoind.cpp:17:
./sync.h:197:10: error: ‘condition_variable’ in namespace ‘std’ does not name a type
std::condition_variable condition;
^~~~~~~~~~~~~~~~~~
./sync.h:198:10: error: ‘mutex’ in namespace ‘std’ does not name a type
std::mutex mutex;
^~~~~
./sync.h: In member function ‘void CSemaphore::wait()’:
./sync.h:206:31: error: ‘mutex’ is not a member of ‘std’
std::unique_lock<std::mutex> lock(mutex);
^~~~~
./sync.h:206:31: error: ‘mutex’ is not a member of ‘std’
./sync.h:206:36: error: template argument 1 is invalid
std::unique_lock<std::mutex> lock(mutex);
^
./sync.h:206:43: error: ‘mutex’ was not declared in this scope
std::unique_lock<std::mutex> lock(mutex);
^~~~~
./sync.h:206:43: note: suggested alternative: ‘putenv’
std::unique_lock<std::mutex> lock(mutex);
^~~~~
putenv
./sync.h:207:9: error: ‘condition’ was not declared in this scope
condition.wait(lock, [&]() { return value >= 1; });
^~~~~~~~~
./sync.h: In member function ‘bool CSemaphore::try_wait()’:
./sync.h:213:30: error: ‘mutex’ is not a member of ‘std’
std::lock_guard<std::mutex> lock(mutex);
^~~~~
./sync.h:213:30: error: ‘mutex’ is not a member of ‘std’
./sync.h:213:35: error: template argument 1 is invalid
std::lock_guard<std::mutex> lock(mutex);
^
./sync.h:213:42: error: ‘mutex’ was not declared in this scope
std::lock_guard<std::mutex> lock(mutex);
^~~~~
./sync.h:213:42: note: suggested alternative: ‘putenv’
std::lock_guard<std::mutex> lock(mutex);
^~~~~
putenv
./sync.h: In member function ‘void CSemaphore::post()’:
./sync.h:223:34: error: ‘mutex’ is not a member of ‘std’
std::lock_guard<std::mutex> lock(mutex);
^~~~~
./sync.h:223:34: error: ‘mutex’ is not a member of ‘std’
./sync.h:223:39: error: template argument 1 is invalid
std::lock_guard<std::mutex> lock(mutex);
^
./sync.h:223:46: error: ‘mutex’ was not declared in this scope
std::lock_guard<std::mutex> lock(mutex);
^~~~~
./sync.h:223:46: note: suggested alternative: ‘putenv’
std::lock_guard<std::mutex> lock(mutex);
^~~~~
putenv
./sync.h:226:9: error: ‘condition’ was not declared in this scope
condition.notify_one();
^~~~~~~~~
In file included from /usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/condition_variable:39:0,
from ./sync.h:11,
from ./util.h:19,
from bitcoind.cpp:17:
/usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/bits/std_mutex.h: In instantiation of ‘void std::unique_lock<_Mutex>::lock() [with _Mutex = CCriticalSection]’:
./sync.h:128:23: required from here
/usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/bits/std_mutex.h:267:17: error: ‘std::unique_lock<CCriticalSection>::mutex_type {aka class CCriticalSection}’ has no member named ‘lock’
_M_device->lock();
~~~~~~~~~~~^~~~
/usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/bits/std_mutex.h: In instantiation of ‘bool std::unique_lock<_Mutex>::try_lock() [with _Mutex = CCriticalSection]’:
./sync.h:137:23: required from here
/usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/bits/std_mutex.h:281:27: error: ‘std::unique_lock<CCriticalSection>::mutex_type {aka class CCriticalSection}’ has no member named ‘try_lock’
_M_owns = _M_device->try_lock();
~~~~~~~~~~~^~~~~~~~
/usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/bits/std_mutex.h: In instantiation of ‘void std::unique_lock<_Mutex>::unlock() [with _Mutex = CCriticalSection]’:
/usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/bits/std_mutex.h:232:10: required from ‘std::unique_lock<_Mutex>::~unique_lock() [with _Mutex = CCriticalSection]’
./sync.h:144:183: required from here
/usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/bits/std_mutex.h:323:17: error: ‘std::unique_lock<CCriticalSection>::mutex_type {aka class CCriticalSection}’ has no member named ‘unlock’
_M_device->unlock();
~~~~~~~~~~~^~~~~~
Makefile:8411: recipe for target 'riecoind-bitcoind.o' failed
make[2]: *** [riecoind-bitcoind.o] Error 1
make[2]: Leaving directory '/usr/src/riecoin/src'
Makefile:9481: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/usr/src/riecoin/src'
Makefile:748: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

These errors seems to be because your mingw gcc compiler version (eventually try using more recent). On what OS version you are trying to build ? What is your mingw gcc version ?

[Pon13]

hi man, thanks for the help !

i re-checked again and since i am in ubuntu 18 (embedded in windows 10) for the first time i missed the following command

Ubuntu Bionic 18.04 1:

Code: Select all

sudo update-alternatives --config x86_64-w64-mingw32-g++ # Set the default mingw32 g++ compiler option to posix.

so i started from scratch and now i have a different problem. when i execute the command

Code: Select all

CONFIG_SITE=$PWD/depends/x86_64-w64-mingw32/share/config.site ./configure --prefix=/

i get the following:

Code: Select all

checking whether __builtin_clzll is declared... yes
checking for MSG_NOSIGNAL... yes
checking for MSG_DONTWAIT... yes
checking for getmemoryinfo... yes
checking for mallopt M_ARENA_MAX... yes
checking for visibility attribute... yes
checking for thread_local support... yes
checking for Linux getrandom syscall... yes
checking for getentropy... yes
checking for getentropy via random.h... yes
checking for sysctl KERN_ARND... no
checking for Berkeley DB C++ headers... no
configure: error: libdb_cxx headers missing, Riecoin Core requires this library for wallet functionality (--disable-wallet to disable wallet functionality)

any thoughts or suggestions? thanks again !

[IGJ]

sudo apt-get install libboost-all-dev libssl-dev libdb++-dev libevent-dev

This will install header files (you will need them to compile the wallet). Highly likely you will have to compile and the libs (or at least some of them) with mingw first so this process will produce .dll/.a/.la files windows libraries files. After that you will be able to compile the wallet source code. If you want to have and graphical interface you will need and:
libprotobuf, protobuf-compiler, libqt4

Compiling windows executables under linux is hard and usually takes a huge amount of time to setup proper environment. So if you going to take that task prepare with elephant patience and to fight with different problems :)
First here is some theory how the things work:

Computers talks only binary numbers language, for humans this language is extremely hard to learn. Thats why programs are written with words that means something for us. To translate our human readable programs to computer language we need compilers (gcc for example) and the process is called compilation. There are two main type of translators first is called compiler the second is called interpreter. Logically you will ask what is the difference, compilers translate the program one time, and write the output to a file, so your program is translated and you can use it anytime you want without the need to translate it again. Interpreters translating the program every time you try to execute it (perl php python java e.t.c) this is done to make your program os and environment independent.
In the world exists many OS but widely used are two of them - windows and linux, they are not fundamentally different but have specific differences, because of these differences windows executable (already translated program to computer language with compiler) can't be directly run under linux and vice versa. To avoid this problem there are cross compilers , these translators can run under one os/platform and to produce translated computer language output for other os/platform (mingw). If you keep reading me to here, then my time is not waste :)
Usually modern programs using external functions that are stored in other programs called libraries. Libraries make programmers life easier, and help them to produce bugs and not working code :). Obviously when cross compile a program that needs external libraries to can functional, you will need to cross compile and these libraries. To make things even more complicated with libs, there are two main method to use them - shared and static. Shared means the libraries are separate as files from your program and these files are accessed when during execution of your program. Static means your libraries are integrated inside the executable file so the program do not need any external programs to can execute (something what maybe you want to do). And now the fun part :) the libraries usually use other libraries so to cross compile library that want another library you will have to cross compile it too.

My advice is your first step to be native compilation of 16.3 (you can see my test on the previous page there I posted all commands you will need to compile the wallet under linux for linux). Then you can start it under linux vm and play with. After that you may start cross compile with all needed libraries. Soon or later I or somebody else from the community will build it for windows and maybe will post nice step by step howto but as you can see this is time eating process and many things can go wrong.

EDIT:
Started to build my environment and needed libs for windows build of 16.3 . Maybe later today will be able to give you windows binary to test, and if it works will write step by step command line how to compile your own 16.3 for windows :)

EDIT2:
Can you test this windows64 build:
http://download.riecoin-community.com/1 ... xv2.tar.gz

[Pttn]

I now have my own Riecoin page. There, you can currently find general links about Riecoin, and download Riecoin-Qt Deb64 and Win64 binaries.
You will even find the full blockchain up to Block 968981 for Riecoin Core 0.16.3, to avoid having to sync everything.
If I had more time, I would complete this page to make it more useful. If you wish IGJ, you can make a redirection from Pttn.Riecoin-Community.com to ric.Pttn.me.

Step by Step how I compiled for Windows:

First, the situation

- It was a cross compiling from Debian 9 (Stable). Unlike what the Docs say, you do not absolutely need Ubuntu 18.04 for this;
- Commit 7667f75;
- https://github.com/riecointeam/riecoin/ ... windows.md was mainly followed and adapted. At some point, Db4.8 will give you trouble, and we will use 5.3 instead. I really think that using 5.3 can avoid some headaches. We should not use that old Db4.8 anymore and upgrade to 5.3. At worst, this is just a blockchain redownload and a few dump/importprivkeys to do (or just send funds to new addresses).

Then, the actual Step by Step:

Install everything:

Code: Select all

# apt install build-essential libtool autotools-dev automake pkg-config bsdmainutils curl git libdb5.3-dev
# apt install g++-mingw-w64-x86-64

Do this, it is also needed for Debian 9, to avoid "Mutex is not a member of Std" errors.

Code: Select all

# update-alternatives --config x86_64-w64-mingw32-g++ # Set the default mingw32 g++ compiler option to posix.

Go to somewhere and download the repository

Code: Select all

git clone https://github.com/riecointeam/riecoin.git Riecoin

Configure to use Db5.3 instead of Db4.8. Else, you will have header problems. To do this, adapt the depends/packages/bdb.mk file to:

Code: Select all

package=bdb
$(package)_version=5.3.28
$(package)_download_path=http://download.oracle.com/berkeley-db
$(package)_file_name=db-$($(package)_version).NC.tar.gz
$(package)_sha256_hash=76a25560d9e52a198d37a31440fd07632b5f1f8f9f2b6d5438f4bc3e7c9013ef
$(package)_build_subdir=build_unix

define $(package)_set_vars
$(package)_config_opts=--disable-shared --enable-cxx --disable-replication
$(package)_config_opts_mingw32=--enable-mingw
$(package)_config_opts_linux=--with-pic
$(package)_cxxflags=-std=c++11
endef

define $(package)_preprocess_cmds
  sed -i.old 's/__atomic_compare_exchange/__atomic_compare_exchange_db/' src/dbinc/atomic.h && \
  sed -i.old 's/atomic_init/atomic_init_db/' src/dbinc/atomic.h src/mp/mp_region.c src/mp/mp_mvcc.c src/mp/mp_fget.c src/mutex/mut_method.c src/mutex/mut_tas.c && \
  sed -i.old 's/WinIoCtl.h/winioctl.h/' src/dbinc/win_db.h && \
  cp -f $(BASEDIR)/config.guess $(BASEDIR)/config.sub dist
endef

define $(package)_config_cmds
  ../dist/$($(package)_autoconf)
endef

define $(package)_build_cmds
  $(MAKE) libdb_cxx-5.3.a libdb-5.3.a
endef

define $(package)_stage_cmds
  $(MAKE) DESTDIR=$($(package)_staging_dir) install_lib install_include
endef

Or, you could try to install Db4.8 in your system, but if 5.3 is already in the repository, why mess with it? And we cannot do add-apt-repository in Debian (and should not have to)...

Some "Bitcoin" strings were forgotten: copy bitcoin.ico to riecoin.ico and bitcoin_testnet.ico to riecoin_testnet.ico in src/qt/res/icons. I said copy, just move will not work (because some corresponding strings need to be replaced somewhere else; you don't need to do it if you just copy. However, you will have an executable with the Bitcoin Core icon).

Now, you should be ready to do the actual building. Go to the depends folder and do (add -j numberOfThreads after make to accelerate if you wish)

Code: Select all

make HOST=x86_64-w64-mingw32

Come back to the main directory and start the second part of the compilation

Code: Select all

cd ..
./autogen.sh
CONFIG_SITE=$PWD/depends/x86_64-w64-mingw32/share/config.site ./configure --prefix=/ -disable-tests -with-incompatible-bdb
make

You are done :D ! You just produced the binary file in src/qt/riecoin-qt.exe ! Execute this in a Windows and enjoy!

Optional : download the file Riecoin.zip available in my page and copy the chainstate and database to your Riecoin directory (by default, C:\Users\user\AppData\Roaming\Riecoin), and you now have an up to date Riecoin Core 0.16.3 on Windows!

[tgspring]

Thank you @Pttn, I am now using your Win64 exe(riecoin-qt0.16.3_7667f75_Win64.exe).

[Pttn]

I now have a fork with correct icons and using Db5.3 instead of 4.8 by default (in a separate branch) for straightforward cross compilation (and compilation without having to pass --with-incompatible-bdb).

While I did a pull request for the icons in RiecoinTeam/Riecoin, I did not for the Db version change.
I am in favor to take advantage of the huge update from 0.10.2 to ditch the prehistoric Db4.8 and use Db5.3 instead (thing that Bitcoin Core cannot do, only because it is so widely used, unlike for us, that they do not want to break wallet compatibility).
This should not introduce problems, and will make the compilation easier in many cases until Bitcoin Core developers finally decide to get rid of Db4.8.
But maybe people have objections for this change, so I am waiting some feedbacks. Else, I will do a pull request for this as well.

Deb64 and Win64 Binaries (commit e16c1349a) now available in my Riecoin page. In practice, there is not really any change, but the icon for the Windows executable is now correct.

How to compile Riecoin Core 0.16.3 in Debian 9 for Linux and Windows available.

[lzknv]

Ok, here is my test:

Fresh install of debian sid (unstable)

mymachine:~# ssh -X root@test

root@test:~# cat /etc/debian_version
buster/sid

root@test:~# apt-get install git autoconf
root@test:~# apt-get install build-essential libboost-all-dev libssl-dev libdb++-dev libevent-dev
root@test:~# apt-get install libqt4-dev libprotobuf-dev protobuf-compiler pkg-config

root@test:~# git clone https://github.com/riecointeam/riecoin
root@test:~# cd riecoin
root@test:~/riecoin# wget http://download.riecoin-community.com/1 ... 1.patch.gz
root@test:~/riecoin# gzip -d riecoind_16.3_openssl_1.1.patch.gz
root@test:~/riecoin# git apply ../riecoind_16.3_openssl_1.1.patch

root@test:~/riecoin# openssl version
OpenSSL 1.1.1 11 Sep 2018

root@test:~/riecoin# ./autogen.sh
root@test:~/riecoin# ./configure --disable-tests --with-incompatible-bdb --with-gui
root@test:~/riecoin# make -j4
(there are some warnings from compiler about comparasion between signed and unsigned , will work on them in separate patch)

root@test:~/riecoin# ldd src/qt/riecoin-qt
linux-vdso.so.1 (0x00007ffe3ddbb000)
libboost_system.so.1.62.0 => /usr/lib/x86_64-linux-gnu/libboost_system.so.1.62.0 (0x00007f139c36e000)
libboost_filesystem.so.1.62.0 => /usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.62.0 (0x00007f139c352000)
libboost_program_options.so.1.62.0 => /usr/lib/x86_64-linux-gnu/libboost_program_options.so.1.62.0 (0x00007f139c2cc000)
libboost_thread.so.1.62.0 => /usr/lib/x86_64-linux-gnu/libboost_thread.so.1.62.0 (0x00007f139c2a0000)
libboost_chrono.so.1.62.0 => /usr/lib/x86_64-linux-gnu/libboost_chrono.so.1.62.0 (0x00007f139c29a000)
libQtGui.so.4 => /usr/lib/x86_64-linux-gnu/libQtGui.so.4 (0x00007f139b5ba000)
libQtNetwork.so.4 => /usr/lib/x86_64-linux-gnu/libQtNetwork.so.4 (0x00007f139b26a000)
libQtDBus.so.4 => /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 (0x00007f139afe8000)
libQtXml.so.4 => /usr/lib/x86_64-linux-gnu/libQtXml.so.4 (0x00007f139ada0000)
libQtCore.so.4 => /usr/lib/x86_64-linux-gnu/libQtCore.so.4 (0x00007f139a8b1000)
libprotobuf.so.10 => /usr/lib/x86_64-linux-gnu/libprotobuf.so.10 (0x0000:7f139a622000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f139a601000)
libdb_cxx-5.3.so => /usr/lib/x86_64-linux-gnu/libdb_cxx-5.3.so (0x00007f139a41b000)
--->>> libssl.so.1.1 => /usr/lib/x86_64-linux-gnu/libssl.so.1.1 (0x00007f139a38a000)
--->>> libcrypto.so.1.1 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 (0x00007f139a0a3000)
libevent_pthreads-2.1.so.6 => /usr/lib/x86_64-linux-gnu/libevent_pthreads-2.1.so.6 (0x00007f1399ea0000)
libevent-2.1.so.6 => /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 (0x00007f1399c4a000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f1399ac7000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f1399931000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f1399917000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f139975a000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f1399750000)
libfontconfig.so.1 => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 (0x00007f139970a000)
libaudio.so.2 => /usr/lib/x86_64-linux-gnu/libaudio.so.2 (0x00007f13994ee000)
libglib-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x00007f13993d1000)
libpng16.so.16 => /usr/lib/x86_64-linux-gnu/libpng16.so.16 (0x00007f139939c000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f139917e000)
libfreetype.so.6 => /usr/lib/x86_64-linux-gnu/libfreetype.so.6 (0x00007f1398ec9000)
libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x00007f1398e75000)
libSM.so.6 => /usr/lib/x86_64-linux-gnu/libSM.so.6 (0x00007f1398c6b000)
libICE.so.6 => /usr/lib/x86_64-linux-gnu/libICE.so.6 (0x00007f1398a4e000)
libXrender.so.1 => /usr/lib/x86_64-linux-gnu/libXrender.so.1 (0x00007f1398844000)
libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x00007f1398632000)
libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007f13984f1000)
libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x00007f139849e000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f1398497000)
/lib64/ld-linux-x86-64.so.2 (0x00007f139cf3f000)
libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x00007f139845a000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007f1398451000)
libXt.so.6 => /usr/lib/x86_64-linux-gnu/libXt.so.6 (0x00007f13981e8000)
libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007f1397fe4000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007f1397f6e000)
libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x00007f1397d65000)
libbsd.so.0 => /lib/x86_64-linux-gnu/libbsd.so.0 (0x00007f1397b4e000)
libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007f1397b24000)
libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 (0x00007f1397a98000)
libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007f1397890000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007f139766a000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 (0x00007f139744d000)
libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x00007f1397131000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x00007f139710f000)

root@test:~/riecoin# mkdir ~/.riecoin16
root@test:~/riecoin# echo "addnode=nodes.riecoin-community.com" > ~/.riecoin16/riecoin.conf
root@test:~/riecoin# ./src/qt/riecoin-qt

I see on my desktop the wallet and syncing headers % growing and think all is working. Not waiting to finish headers sync and close the window.

--------------------------------------
root@test:~/riecoin# apt-get install libssl1.0-dev
root@test:~/riecoin# make clean
root@test:~/riecoin# ./configure --disable-tests --with-incompatible-bdb --with-gui
root@test:~/riecoin# make -j4
root@test:~/riecoin# ldd src/qt/riecoin-qt
linux-vdso.so.1 (0x00007ffc3567e000)
libboost_system.so.1.62.0 => /usr/lib/x86_64-linux-gnu/libboost_system.so.1.62.0 (0x00007fae22634000)
libboost_filesystem.so.1.62.0 => /usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.62.0 (0x00007fae22618000)
libboost_program_options.so.1.62.0 => /usr/lib/x86_64-linux-gnu/libboost_program_options.so.1.62.0 (0x00007fae22592000)
libboost_thread.so.1.62.0 => /usr/lib/x86_64-linux-gnu/libboost_thread.so.1.62.0 (0x00007fae22566000)
libboost_chrono.so.1.62.0 => /usr/lib/x86_64-linux-gnu/libboost_chrono.so.1.62.0 (0x00007fae22560000)
libQtGui.so.4 => /usr/lib/x86_64-linux-gnu/libQtGui.so.4 (0x00007fae21880000)
libQtNetwork.so.4 => /usr/lib/x86_64-linux-gnu/libQtNetwork.so.4 (0x00007fae21530000)
libQtDBus.so.4 => /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 (0x00007fae212ae000)
libQtXml.so.4 => /usr/lib/x86_64-linux-gnu/libQtXml.so.4 (0x00007fae21066000)
libQtCore.so.4 => /usr/lib/x86_64-linux-gnu/libQtCore.so.4 (0x00007fae20b77000)
libprotobuf.so.10 => /usr/lib/x86_64-linux-gnu/libprotobuf.so.10 (0x00007fae208e8000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fae208c7000)
libdb_cxx-5.3.so => /usr/lib/x86_64-linux-gnu/libdb_cxx-5.3.so (0x00007fae206e1000)
--->>> libssl.so.1.0.2 => /usr/lib/x86_64-linux-gnu/libssl.so.1.0.2 (0x00007fae20479000)
--->>> libcrypto.so.1.0.2 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.2 (0x00007fae20017000)
libevent_pthreads-2.1.so.6 => /usr/lib/x86_64-linux-gnu/libevent_pthreads-2.1.so.6 (0x00007fae1fe14000)
libevent-2.1.so.6 => /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 (0x00007fae1fbbe000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fae1fa3b000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fae1f8a5000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fae1f88b000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fae1f6ce000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fae1f6c4000)
libfontconfig.so.1 => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 (0x00007fae1f67e000)
libaudio.so.2 => /usr/lib/x86_64-linux-gnu/libaudio.so.2 (0x00007fae1f462000)
libglib-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x00007fae1f345000)
libpng16.so.16 => /usr/lib/x86_64-linux-gnu/libpng16.so.16 (0x00007fae1f310000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007fae1f0f2000)
libfreetype.so.6 => /usr/lib/x86_64-linux-gnu/libfreetype.so.6 (0x00007fae1ee3d000)
libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x00007fae1ede9000)
libSM.so.6 => /usr/lib/x86_64-linux-gnu/libSM.so.6 (0x00007fae1ebdf000)
libICE.so.6 => /usr/lib/x86_64-linux-gnu/libICE.so.6 (0x00007fae1e9c2000)
libXrender.so.1 => /usr/lib/x86_64-linux-gnu/libXrender.so.1 (0x00007fae1e7b8000)
libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x00007fae1e5a6000)
libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007fae1e465000)
libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x00007fae1e412000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fae1e40b000)
/lib64/ld-linux-x86-64.so.2 (0x00007fae23203000)
libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x00007fae1e3ce000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007fae1e3c5000)
libXt.so.6 => /usr/lib/x86_64-linux-gnu/libXt.so.6 (0x00007fae1e15c000)
libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007fae1df58000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007fae1dee2000)
libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x00007fae1dcd9000)
libbsd.so.0 => /lib/x86_64-linux-gnu/libbsd.so.0 (0x00007fae1dac2000)
libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007fae1da98000)
libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 (0x00007fae1da0c000)
libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007fae1d804000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007fae1d5de000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 (0x00007fae1d3c1000)
libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x00007fae1d0a5000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x00007fae1d083000)

root@test:~/riecoin# ./src/qt/riecoin-qt

I see on my desktop the wallet and syncing headers % growing so I assume it is working again.

I think all is working.

I will leave the wallet 16.3 with libssl 1.1.1 during the night to do full sync but dont see reasons it will not work. I guess the things will be same on current stable debian release (debian 9 - stretch). Will be useful if izknv can make test on ubuntu too.

Hi IGJ, thanks for posting the detailed commands! I managed to compile without error message on Ubuntu 18.04. However the binary does not function.

src/qt/riecoin-qt exists but running it does not show anything - no error, no qt window.
riecoind -version shows: v0.16.3-(something)
riecoind: segmentation fault(core dumped)

Any ideas where I can get better error messages to help diagnosing? Thanks!

[lzknv]

I now have a fork with correct icons and using Db5.3 instead of 4.8 by default (in a separate branch) for straightforward cross compilation (and compilation without having to pass --with-incompatible-bdb).

While I did a pull request for the icons in RiecoinTeam/Riecoin, I did not for the Db version change.
I am in favor to take advantage of the huge update from 0.10.2 to ditch the prehistoric Db4.8 and use Db5.3 instead (thing that Bitcoin Core cannot do, only because it is so widely used, unlike for us, that they do not want to break wallet compatibility).
This should not introduce problems, and will make the compilation easier in many cases until Bitcoin Core developers finally decide to get rid of Db4.8.
But maybe people have objections for this change, so I am waiting some feedbacks. Else, I will do a pull request for this as well.

Deb64 and Win64 Binaries (commit e16c1349a) now available in my Riecoin page. In practice, there is not really any change, but the icon for the Windows executable is now correct.

How to compile Riecoin Core 0.16.3 in Debian 9 for Linux and Windows available.

Hi, I followed your instructions and managed to compile and run riecoin-qt on debian. Thank you very much for putting these instructions together.

I highly recommend to add the following tips to your how-to, so that future users can save hours of time and be less frustrated:

apt install libdb5.3++-dev (I spent an hour to figure out ++ is needed to avoid a compile error)
apt install libevent-dev
....and more. I also found this doc quite useful.

configure --disable-tests --with-gui