having a hard time getting gnuradio to work with my dvb-t usb stick latest attempt has been to move to using pybomb, e.g.
https://smyl.es/how-to-install-gnu-radio-fftw-rtl-sdr-grosmosdr-and-more-using-pybombs-with-dependencies-by-rpmdeb-or-build-from-source/ originally i installed gnuradio and gnuradio-dev via apt-get install, under ubuntu 14.04 which gave me gnuradio v2.7.2.1 i then tried to build gr-osomosdr but it failed (i took the cmake route as per: http://sdr.osmocom.org/trac/wiki/GrOsmoSDR) maybe i don't need to build gr-osmosdr if it is already packaged up with gnuradio, how could i see if the block is there, i.e. what dir would it be in if it existed? unfortunately pybomb fails with the following error: $sudo ./pybombs install gnuradio [ 29%] Built target _wavelet_swig_swig_tag make[2]: *** No rule to make target `/usr/include/gnuradio/blocks/vector_sink_c.h', needed by `gr-blocks/swig/blocks_swig1_gr_blocks_swig_a6e57.cpp'. Stop. make[1]: *** [gr-blocks/swig/CMakeFiles/blocks_swig1_gr_blocks_swig_a6e57.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs.... [ 29%] Built target pmt_swig_gnuradio_runtime_swig_7dd5e [ 29%] Built target blocks_swig0_gr_blocks_swig_a6e57 [ 33%] Built target gnuradio-runtime make: *** [all] Error 2 ERROR:root:PyBOMBS Make step failed for package (gnuradio) please see bash output above for a reason (hint: look for the word Error) also gr-osmosdr also fails: $sudo ./pybombs install gr-osmosdr Built target _wxgui_swig_swig_tag make[2]: *** No rule to make target `/usr/include/gnuradio/blocks/vector_sink_c.h', needed by `gr-blocks/swig/blocks_swig1_gr_blocks_swig_a6e57.cpp'. Stop. make[1]: *** [gr-blocks/swig/CMakeFiles/blocks_swig1_gr_blocks_swig_a6e57.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs.... [ 29%] Built target pmt_swig_gnuradio_runtime_swig_7dd5e [ 29%] Built target blocks_swig0_gr_blocks_swig_a6e57 [ 33%] Built target gnuradio-runtime make: *** [all] Error 2 ERROR:root:PyBOMBS Make step failed for package (gnuradio) please see bash output above for a reason (hint: look for the word Error) anyone else seen this sort of issue?
