I would probably use pybombs (it is how I install on x86_32/x86_64):
https://www.gnuradio.org/blog/pybombs-the-what-the-how-and-the-why has a good overview, but I would use the manual commands from the current README.md at https://github.com/gnuradio/pybombs
Basically pybombs looks at your system, determines what is missing and installs required packages (git, compilers,…), and then almost everything else is downloaded, compiled and installed from the latest source code using the current release/maintenance branch. It is slower to compile everything from source code, but the folder where everything is installed will be in a known good working state. Pybombs may have problems with some unique/uncommon distributions, but it should work for anything based on Debian (deb e.g. Ubuntu, Raspbian), Fedora (rpm e.g. RedHat, CentOS), Arch (pacman) and probably OSX (port).
You could even use pybombs to install the just released (well about 3 weeks ago) gnuradio 3.8 (“pybombs install gnuradio38”) if you really want lots of new and unexplored problems to deal with, since they have a recipe for that, but the default install is gnuradio37 (https://github.com/gnuradio/gr-recipes), and every module still expects to use that as the default. There is a lot of wisdom in picking the well travelled path of least resistance, where most problems have been found, fully dissected and solved. And with a standard “pybombs install gnuradio” you know that a simple “pybombs install gr-limesdr” will add all required dependencies. to get a lime board working with gnuradio 3.7.
The only thing that confused me about pybombs initially when I used it was that before I could use any of the installed programs (grc,gqrx,limesuite,), either after a reboot or on opening a new terminal was that I needed to do something like the following (depending on which directory you initially picked to install) to modify my environment to see that executables:
$ source ~/prefix/setup_env.sh
$ gnuradio-companion