gnuradio | GNU Radio – the Free and Open Software Radio Ecosystem | Navigation library

I think it is RAM issue ,check here and here.

I suggest you compile boost alone first:

Perhaps gnuradio creates threads from its own C API? – user23952

Exactly. GNU Radio is a heavily multithreaded application.

Can you explain to me how to detect threads created by python and kill them?

You can "kill" processes, you can't "kill" threads - you can interrupt/join them (which is akin in the sense that it means they don't get scheduled anymore, but different in the sense that the resources allocated to them don't disappear – because threads don't hold own resources (aside from a stack), it's the process that does.

Note that existing threads in themselves are not inherently a problem - it's perfectly normal for a program to have dormant threads that get cleaned up on exit by the operating system and not earlier; threads serve various purposes, including things like handling signals, waiting for RPC connections, managing other resources... which might not even occur in your case.

Do you know how to exit the gr-osmosdr block properly?

This might very well be a problem of the specific driver source encapsulated in the osmosdr source.

Probably this all exits "properly", you've not actually described anything that goes wrong!

You can't them (you could look for Volk instead of VOLK, but it might break things in other places) - you also don't have to, it's just warnings, so no action is needed.

you need to uninstall your currently installed GNU Radio, your currently installed UHD (make doubly sure you've removed both), then you need to install your self-built UHD, then build and install GNU Radio. Make sure not to accidentally install your operating system's UHD again!

You cannot make a GNU Radio that was built with a different version of UHD work with your version; you need to built it.

Your traceback shows that the file C:\Users\User1\miniforge3\envs\gnuradio\lib\site-packages\gnuradio\qtgui\range.py has this line:

I think you are missing swig/dependencies or PYTHONPATH. I had the same issue, and was able to resolve it by following these fixes:

1. Install dependencies specific to your environment (including swig): https://wiki.gnuradio.org/index.php/UbuntuInstall#Bionic_Beaver_.2818.04.29_through_Eoan_Ermine_.2819.10.29
2. Configure PYTHONPATH and/or LD_LIBRARY_PATH according to these steps: https://wiki.gnuradio.org/index.php/ModuleNotFoundError

(Note that order may matter according to this case: https://lists.gnu.org/archive/html/discuss-gnuradio/2016-03/msg00065.html)

$CMAKE_INSTALL_PREFIX/share/zsh/site-functions is the right place.

It is the same with man pages, info pages, pkg-config path, binaries and libraries and whatever else. On a default install, man will only look in predefined places like /usr/share/man and /usr/local/share/man.

If someone decides to install to /opt/gnuradio or whatever, it is then also their responsibility to ensure that they set $PATH, $MANPATH $INFOPATH and whatever else accordingly. It is the same for $fpath. The best software can do is ensure that they stick to established conventions and not to spew files elsewhere on the filesystem outside of $PREFIX.

If Ubuntu wants to be clever and invent their own vendor-completion directories then a consequence of that is that is that they need to patch everything they package that includes a zsh completion. That's their problem because they created the problem for themselves.