Hennadii Stepanov

Tested on Debian 9.5 with different repos: `gitianuser@debian:~$ apt list -a debootstrap` ``` Listing... Done debootstrap/unstable,now 1.0.109 all [installed] debootstrap/testing 1.0.108 all debootstrap/stretch-backports 1.0.100~bpo9+1 all debootstrap/stable 1.0.89 all ``` -...

@real-or-random > @hebasto If you're Concept ACK, are you willing to work on an equivalent PR for CMake? Please consider https://github.com/bitcoin-core/secp256k1/pull/1532.

https://github.com/chaincodelabs/libmultiprocess/issues/4#issue-473482967: > ... would like to create libmultiprocess packages... See https://github.com/chaincodelabs/libmultiprocess/pull/96.

> Are there some docs somewhere that suggest this? https://gcc.gnu.org/onlinedocs/gcc/Gcov-and-Optimization.html ~UPD. The code has been taken from https://github.com/flux-framework/flux-core/pull/4828/commits/a9bf41730a9ae147a4616b01a0a005740a6d29af.~

Addressed @ajtowns's feedback. Added comments. Updated the PR description.

Ported to the CMake-based build system in https://github.com/hebasto/bitcoin/pull/202.

I suggest to add https://github.com/bitcoin-core/gui/pull/812 and https://github.com/bitcoin-core/gui/pull/813.

The buildsystem related stuff has been ported to the CMake-based buildsystem in https://github.com/hebasto/bitcoin/pull/317.

> I guess the idea is that there's basically nothing worth salvaging from our current Android build procedure? The commit history keeps everything we might need when restoring Android builds.

> > I guess the idea is that there's basically nothing worth salvaging from our current Android build procedure? > > Not sure about that. i think the idea is...