I -strongly- recommend against setting the CMAKE_INSTALL_PREFIX to a system directory such as /usr when you are building from source (not using a package manager)! You never know what you're going to overwrite from the system itself, which can cause library loading breakage. When installing anything from source, use a "local" directory of some sort ... /usr/local is perfectly fine! Then, set environment variables to find the installed stuff: PATH, PYTHONPATH, PKG_CONFIG_PATH, MANPATH, INFOPATH, etc... That said, on OSX just please don't set DYLD_LIBRARY_PATH except for temporarily for testing purposes; doing so can really mess up application execution! My US$0.02 worth ... - MLD
On Fri, Nov 15, 2019 at 8:42 AM Glen I Langston <
address@hidden> wrote:
Hi Kevin,
I’ve run into this too.
The instructions tell you the solution after the build commands
change the “cmake” line to
cmake -DCMAKE_INSTALL_PREFIX=/usr .
and rebuild all
and do the copy step they suggest on site
https://wiki.analog.com/resources/tools-software/linux-software/gnuradio
(Either
cp -r /usr/local/lib/python2.7/dist-packages/gnuradio/iio /usr/lib/python2.7/dist-packages/gnuradio/
or
cp -r /usr/local/lib/python2.7/site-packages/gnuradio/iio /usr/lib/python2.7/site-packages/gnuradio/
or
some similar combination, depending on where your build files end up after install
)
Good luck.
Glen
The packages can go into 4 different directories (on Ubuntu, maybe only 2 on mac)
/usr/local/lib/python2.7/site-packages
/usr/lib/python2.7/site-packages
and
/usr/local/lib/python2.7/dist-packages
/usr/lib/python2.7/dist-packages
on Ubuntu
I’ve been copying all of the "site-packages" stuff into “dist-packages”
and creating symbolic link from dist-packages to site-packages.
(Not really recommended, but I do it anyway).
Good Luck
--