Re: [Discuss-gnuradio] PyBOMBS install gnuradio 3.7.4

[Activecat]

On Tue, May 20, 2014 at 11:06 AM, Activecat <address@hidden> wrote:

I've just reinstalled gnuradio yesterday, using PyBOMBS.

The newly installed version is gnuradio 3.7.4. The installation succeeded, but it then failed to compile my custom module which worked flawlessly with previous gnuradio installation.

The previous version was gnuradio 3.7.3 which was installed using build-gunuradio, which had no problem at all.

Compilation error:

    Linking CXX shared library libgnuradio-activecat.so
    [ 71%] Built target gnuradio-activecat
    Scanning dependencies of target test-activecat
    [ 72%] Building CXX object lib/CMakeFiles/test-activecat.dir/test_activecat.cc.o
    [ 74%] Building CXX object lib/CMakeFiles/test-activecat.dir/qa_activecat.cc.o
    Linking CXX executable test-activecat
    /usr/bin/ld: CMakeFiles/test-activecat.dir/test_activecat.cc.o: undefined reference to symbol '_ZN5boost10filesystem6detail16create_directoryERKNS0_4pathEPNS_6system10error_codeE'
    /usr/bin/ld: note: '_ZN5boost10filesystem6detail16create_directoryERKNS0_4pathEPNS_6system10error_codeE' is defined in DSO /home/sgku/download/gnuradio/target/lib/libboost_filesystem-mt.so.1.53.0 so try adding it to the linker command line
    /home/sgku/download/gnuradio/target/lib/libboost_filesystem-mt.so.1.53.0: could not read symbols: Invalid operation
    collect2: error: ld returned 1 exit status
    make[2]: *** [lib/test-activecat] Error 1
    make[1]: *** [lib/CMakeFiles/test-activecat.dir/all] Error 2
    make: *** [all] Error 2

The problem has been solved.

Solution: Reinstall gnuradio using PyBOMBS, make sure prefix=/usr/local

Note:

During PyBOMBS install wizard, we are prompted for prefix, which defaults to ../target

If we just press ENTER to accept the default value, then the prefix becomes something like /home/user1/download/gnuradio/target.
But regardless of what has been configured for the prefix, the OOT (out-of-tree module) will be install into /usr/local.

Since the newly generated setup_env.sh does not include /usr/local, above error could occur.