Update build-unix.md

[Quezacoatl1]

Added Raspberry guide. Probably we should add the BerkeleyDB 4.8 guide also to the other guides?
Also I needed sudo to install the daemon in the last step. I guess this is also necessary for the common user on Linux in general

[tomasbrod]

sudo make install should not be used on any linux system with package manager. It would make it hard to remove, or update, later. For debian checkinstall(...) should be used.

[denravonska]

@tomasbrod TIL :)

[Quezacoatl1]

I had to use sudo in my case I think :(

[iFoggz]

would have to use sudo if compiling under a normal privileged account. if compiling as root you don't need sudo. least in ubuntu anyway

[TheCharlatan]

The discussion is not about using sudo. Priviledge escalation should be used when writing to root. Checkinstall should be used over make install. make install is fine for some systems, but on Raspbian (which is Debian based), checkinstall should be used instead.

[Quezacoatl1]

so I could try "checkinstall" instead of "sudo make install" ? I will check and report back when I tried

[tomasbrod]

If you already run something in there with sudo, chances are it messed up permissions. Either delete the folder and start from scratch, or fix the permissions.

[denravonska]

@Quezacoatl1 Did you get a chance to try it out?

[denravonska]

Is this needed when we have Depends? It should be the only supported way of building a wallet.

[TheCharlatan]

Arguably cross compiling is much faster, however it does not necessarily preserve back-compatibility. I am still waiting for bitcoin to release a new back compatibility patch for ubuntu 18.04's c libraries. I believe in freedom of choice when it comes to ones dependencies. There are good reasons for not linking everything statically.

[denravonska]

@TheCharlatan That is true but I still think we should officially only support Depends as the way to build a wallet with known dependencies. With "support" I mean "this is the way we know works. If you do it any other way it may or may not work, and you are on your own". I don't think there's a need to also provide instructions for manually compiling individual dependencies when we have a system in place to do so.

[tomasbrod]

About the sudo. The build steps (autogen.sh, configure, make) should be executed without sudo. The last one, make install, requires sudo. However on debian, checkinstall -D make install should be used, see debian admin. Package installation, like apt install libsomething, also requires sudo.

[G-UK]

I've just been trying checkinstall as suggested on the latest testnet builds. One problem is that it takes whatever is after the hyphen (-) in the Package name to be the version.

So, as we use "Gridcoin-Research" as our name, checkinstall fails with a bad version name unless you manually override it.

It thinks "Gridcoin" is the application name and "Research" is the application version.

Edit:
I suppose an install script could be created where the version and release are pulled from the current build, something like this.

#!/bin/bash
sudo checkinstall \
    --maintainer="https://github.com/gridcoin-community" \    
    --pkgname=gridcoinresearch \
    --pkgversion="4.0.1.3" \
    --pkgrelease="TESTNET" \
    --pkglicense="MIT" \
    --pkgsource="https://github.com/gridcoin-community/Gridcoin-Research"

[jamescowens]

This was superseded by #1686.