gr-gsm make issue with osmosdr module

[Martin Spears]

I am trying to make gr-gsm I do believe I have all the nessesary support 
libraries:

using :

https://osmocom.org/projects/gr-gsm/wiki/Installation
Installation - gr-gsm - Open Source Mobile 
Communications
Installation¶ There are many ways to install gr-gsm: . Manual compilation and 
installation; Installation from distribution's packages; Compilation and 
installation with use of Pybombs installation manager
osmocom.org
as my starting point.
cmake output

~/src/gr-gsm/build$ cmake ../
-- The CXX compiler identification is GNU 7.4.0
-- The C compiler identification is GNU 7.4.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Build type not specified: defaulting to release.
-- Found LOG4CPP: /usr/lib/x86_64-linux-gnu/liblog4cpp.so
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.1")
-- Checking for module 'gmp'
--   No package 'gmp' found
-- Found GMP: /usr/lib/x86_64-linux-gnu/libgmpxx.so
-- Checking for module 'mpir >= 3.0'
--   No package 'mpir' found
-- Could NOT find MPIR (missing: MPIRXX_LIBRARY MPIR_LIBRARY MPIR_INCLUDE_DIR)
-- Found MPLIB: /usr/lib/x86_64-linux-gnu/libgmpxx.so
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Boost version: 1.65.1
-- Found the following Boost libraries:
--   date_time
--   program_options
--   filesystem
--   system
--   regex
--   thread
--   unit_test_framework
--   chrono
--   atomic
-- Found VOLK: Volk::volk
-- User set python executable /usr/bin/python3
-- Found PythonInterp: /usr/bin/python3 (found version "3.6.8")
-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython3.6m.so (found suitable 
exact version "3.6.8")
-- Checking for module 'fftw3f >= 3.0'
--   Found fftw3f , version 3.3.7
-- Found FFTW3f: /usr/lib/x86_64-linux-gnu/libfftw3f.so
-- Found Git: /usr/bin/git
-- Extracting version information from git describe...
-- Found Doxygen: /usr/bin/doxygen (found version "1.8.13") found components:  
doxygen dot
-- Checking for module 'libosmocore'
--   Found libosmocore, version 1.2.0.65-d0e8
-- Found libosmocore: /usr/local/lib/libosmocore.so
-- Checking for module 'libosmocodec'
--   Found libosmocodec, version 1.2.0.65-d0e8
-- Found libosmocodec: /usr/local/lib/libosmocodec.so
-- Checking for module 'libosmocoding'
--   Found libosmocoding, version 1.2.0.65-d0e8
-- Found libosmocoding: /usr/local/lib/libosmocoding.so
-- Checking for module 'libosmogsm'
--   Found libosmogsm, version 1.2.0.65-d0e8
-- Found libosmogsm: /usr/local/lib/libosmogsm.so
-- Loading build date Tue, 19 Nov 2019 15:07:50 into constants...
-- Loading version v0.41.1-346-g2efaa49e into constants...
-- Using install prefix: /usr/local
-- Building for version: v0.41.1-346-g2efaa49e / 1.0.0git
-- No C++ unit tests... skipping
--
-- Checking for module SWIG
-- Found SWIG version 3.0.12.
-- Found SWIG: /usr/bin/swig3.0
-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython3.6m.so (found version 
"3.6.8")
-- Configuring done
-- Generating done
-- Build files have been written to: /home/martin/src/gr-gsm/build


make output:
[ 73%] Generating grgsm_livemon
<<< Welcome to GNU Radio Companion Compiler 3.8.0.0 >>>

Block paths:
/home/martin/.grc_gnuradio
/home/martin/src/gr-gsm/grc
/usr/share/gnuradio/grc/blocks
/usr/local/share/gnuradio/grc/blocks

>>> Loading: /home/martin/src/gr-gsm/apps/grgsm_livemon.grc
Traceback (most recent call last):
  File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
from .device import *
  File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, in 

import osmosdr
ModuleNotFoundError: No module named 'osmosdr'
Traceback (most recent call last):
  File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
from .device import *
  File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, in 

import osmosdr
ModuleNotFoundError: No module named 'osmosdr'
Traceback (most recent call last):
  File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
from .device import *
  File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, in 

import osmosdr
ModuleNotFoundError: No module named 'osmosdr'
Traceback (most recent call last):
  File "/home/martin/sr

Re: qt-gui problems with GNU 3.8

[Mark Koenig]

Marcus,

Here is some feedback regarding using the rpms you helped me create.

I can run ‘cmake’ with no errors, but running ‘make’ I see the errors below 
with respect to the qt-gui package.  Any advice on how to fix this problem?

Thank you

Mark

#38 2179. [ 79%] Generating 
__/include/gnuradio/qtgui/moc_spectrumdisplayform.cpp
#38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
#38 2179. [ 79%] Generating __/include/gnuradio/qtgui/moc_displayform.cpp
#38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
#38 2179. [ 79%] Generating __/include/gnuradio/qtgui/moc_timedisplayform.cpp
#38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
#38 2179. [ 79%] Generating __/include/gnuradio/qtgui/moc_timecontrolpanel.cpp
#38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
#38 2179. [ 79%] Generating 
__/include/gnuradio/qtgui/moc_timerasterdisplayform.cpp
#38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
#38 2179. [ 79%] Generating __/include/gnuradio/qtgui/moc_freqdisplayform.cpp
#38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
#38 2179. [ 79%] Generating __/include/gnuradio/qtgui/moc_freqcontrolpanel.cpp
#38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
#38 2179. [ 79%] Generating 
__/include/gnuradio/qtgui/moc_constellationdisplayform.cpp
#38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
#38 2179. [ 80%] Generating 
__/include/gnuradio/qtgui/moc_waterfalldisplayform.cpp
#38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
#38 2179. [ 80%] Generating 
__/include/gnuradio/qtgui/moc_histogramdisplayform.cpp
#38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
#38 2179. [ 80%] Generating __/include/gnuradio/qtgui/moc_numberdisplayform.cpp
#38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
#38 2179. [ 80%] Generating __/include/gnuradio/qtgui/moc_vectordisplayform.cpp
#38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
#38 2179. [ 80%] Generating __/include/gnuradio/qtgui/moc_form_menus.cpp
#38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
#38 2179. [ 80%] Generating __/include/gnuradio/qtgui/moc_DisplayPlot.cpp
#38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
#38 2179. [ 80%] Generating 
__/include/gnuradio/qtgui/moc_FrequencyDisplayPlot.cpp
#38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
#38 2179. [ 80%] Generating 
__/include/gnuradio/qtgui/moc_TimeDomainDisplayPlot.cpp
#38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
#38 2179. [ 80%] Generating 
__/include/gnuradio/qtgui/moc_TimeRasterDisplayPlot.cpp
#38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
#38 2179. [ 80%] Generating 
__/include/gnuradio/qtgui/moc_WaterfallDisplayPlot.cpp
#38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
#38 2179. [ 80%] Generating 
__/include/gnuradio/qtgui/moc_ConstellationDisplayPlot.cpp
#38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
#38 2179. [ 81%] Generating 
__/include/gnuradio/qtgui/moc_HistogramDisplayPlot.cpp
#38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
#38 2179. [ 81%] Generating __/include/gnuradio/qtgui/moc_VectorDisplayPlot.cpp
#38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
#38 2179. [ 81%] Generating moc_edit_box_msg_impl.cpp
#38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
#38 2180. [ 81%] Generating 
__/include/gnuradio/qtgui/moc_spectrumdisplayform.cpp
#38 2180. standard input:0: Note: No relevant classes found. No output 
generated.
#38 2180. [ 81%] Building CXX object 
gr-qtgui/lib/CMakeFiles/gnuradio-qtgui.dir/__/include/gnuradio/qtgui/moc_spectrumdisplayform.cpp.o
#38 2180. c++: error: 
/opt/truearrow/6.3/src/gnuradio/build/gr-qtgui/lib/__/include/gnuradio/qtgui/moc_spectrumdisplayform.cpp:
 No such file or directory
#38 2180. c++: fatal error: no input files
#38 2180. compilation terminated.
#38 2180. make[2]: *** 
[gr-qtgui/lib/CMakeFiles/gnuradio-qtgui.dir/build.make:714: 
gr-qtgui/lib/CMakeFiles/gnuradio-qtgui.dir/__/include/gnuradio/qtgui/moc_spectrumdisplayform.cpp.o]
 Error 1
#38 2180. make[1]: *** [CMakeFiles/Makefile2:9430: 
gr-qtgui/lib/CMakeFiles/gnuradio-qtgui.dir/all] Error 2
#38 2180. make: *** [Makefile:141: all] Error 2
#38 DONE 2180.6s




On 11/15/19, 3:50 PM, "Müller, Marcus   (CEL)"  wrote:

Ah, it's the same old blues; need to have qt(4)-devel packaged for qwt.

(What I've tried is: Run Fedora as host, and have a podman (or docker,
as if I care, replace "podman" by "do

Re: qt-gui problems with GNU 3.8

[CEL]

That sounds like `moc` is misbehaving. Or CMake is and the Makefiles
aren't correctly regenerating all necessary files if subsets are
already there.

a) If you haven't, uninstall all potentially half-installed GNU Radios
(don't ask), purge your build folder and cmake; make -j8 again
b) If that doesn't solve it, we'll need to look at the paths: Do the
paths (starting with __ in your, I presume censored, email) look right?

Best regards,
Marcus

On Tue, 2019-11-19 at 15:31 +, Mark Koenig wrote:
> Marcus,
> 
> Here is some feedback regarding using the rpms you helped me create.
> 
> I can run ‘cmake’ with no errors, but running ‘make’ I see the errors below 
> with respect to the qt-gui package.  Any advice on how to fix this problem?
> 
> Thank you
> 
> Mark
> 
> #38 2179. [ 79%] Generating 
> __/include/gnuradio/qtgui/moc_spectrumdisplayform.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
> generated.
> #38 2179. [ 79%] Generating __/include/gnuradio/qtgui/moc_displayform.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
> generated.
> #38 2179. [ 79%] Generating __/include/gnuradio/qtgui/moc_timedisplayform.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
> generated.
> #38 2179. [ 79%] Generating __/include/gnuradio/qtgui/moc_timecontrolpanel.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
> generated.
> #38 2179. [ 79%] Generating 
> __/include/gnuradio/qtgui/moc_timerasterdisplayform.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
> generated.
> #38 2179. [ 79%] Generating __/include/gnuradio/qtgui/moc_freqdisplayform.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
> generated.
> #38 2179. [ 79%] Generating __/include/gnuradio/qtgui/moc_freqcontrolpanel.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
> generated.
> #38 2179. [ 79%] Generating 
> __/include/gnuradio/qtgui/moc_constellationdisplayform.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
> generated.
> #38 2179. [ 80%] Generating 
> __/include/gnuradio/qtgui/moc_waterfalldisplayform.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
> generated.
> #38 2179. [ 80%] Generating 
> __/include/gnuradio/qtgui/moc_histogramdisplayform.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
> generated.
> #38 2179. [ 80%] Generating 
> __/include/gnuradio/qtgui/moc_numberdisplayform.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
> generated.
> #38 2179. [ 80%] Generating 
> __/include/gnuradio/qtgui/moc_vectordisplayform.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
> generated.
> #38 2179. [ 80%] Generating __/include/gnuradio/qtgui/moc_form_menus.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
> generated.
> #38 2179. [ 80%] Generating __/include/gnuradio/qtgui/moc_DisplayPlot.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
> generated.
> #38 2179. [ 80%] Generating 
> __/include/gnuradio/qtgui/moc_FrequencyDisplayPlot.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
> generated.
> #38 2179. [ 80%] Generating 
> __/include/gnuradio/qtgui/moc_TimeDomainDisplayPlot.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
> generated.
> #38 2179. [ 80%] Generating 
> __/include/gnuradio/qtgui/moc_TimeRasterDisplayPlot.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
> generated.
> #38 2179. [ 80%] Generating 
> __/include/gnuradio/qtgui/moc_WaterfallDisplayPlot.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
> generated.
> #38 2179. [ 80%] Generating 
> __/include/gnuradio/qtgui/moc_ConstellationDisplayPlot.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
> generated.
> #38 2179. [ 81%] Generating 
> __/include/gnuradio/qtgui/moc_HistogramDisplayPlot.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
> generated.
> #38 2179. [ 81%] Generating 
> __/include/gnuradio/qtgui/moc_VectorDisplayPlot.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
> generated.
> #38 2179. [ 81%] Generating moc_edit_box_msg_impl.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
> generated.
> #38 2180. [ 81%] Generating 
> __/include/gnuradio/qtgui/moc_spectrumdisplayform.cpp
> #38 2180. standard input:0: Note: No relevant classes found. No output 
> generated.
> #38 2180. [ 81%] Building CXX object 
> gr-qtgui/lib/CMakeFiles/gnuradio-qtgui.dir/__/include/gnuradio/qtgui/moc_spectrumdisplayform.cpp.o
> #38 2180. c++: error: 
> /opt/truearrow/6.3/src/gnuradio/build/gr-qtgui/lib/__/include/gnuradio/qtgui/moc_spectrumdisplayform.cpp:
>  No such file or direct

Re: discuss-gnuradio Subject prefix (Was: Contribute to GNU radio)

[CEL]

I frankly don't fully follow – instead of writing a filter that sorts
away your emails in folders, you could also write a filter that
prefixes them with [tags]? I don't know yahoo's mail interface very
well, but I'd be surprised if that functionality didn't exist.

Also, it's completely up to your mail client to show all unread emails
in an inbox; my K9 for android does that beautifully.

On Tue, 2019-11-19 at 08:15 +, Bogdan Diaconescu wrote:
> I understand the technical motivation behind this. Frankly if the e-mails are 
> filtered into a folder they will stay there unread forever. I like to pick 
> e-mails based on their subject and list for reading. If this change remains 
> without [gnuradio-] preamble I need to find a way to easily identify the 
> list. This seems a let's bring in technology to make life even more complex.
> 
> Bogdan
> 
> 
> 
> On Monday, November 18, 2019, 1:27:47 PM GMT+2, Adrian Musceac 
>  wrote:
> 
> 
> You're probably right, but I have to use the canine mailer with a flat view 
> on my phone due to screen limitations, and I suppose some other people do as 
> well.
> For normal desktop view it's not such a big deal.
> 
> Adrian
> 
> On November 18, 2019 10:59:00 AM UTC, "N. Benes"  wrote:
> > Hi everyone,
> > 
> > FYI, here is the general announcement of and motivation for the changes:
> > 
> > > https://lists.gnu.org/archive/html/savannah-hackers-public/2019-06/msg00018.html
> > > https://lists.gnu.org/archive/html/savannah-hackers-public/2019-09/msg00016.html
> > 
> > Adrian Musceac:
> > > I have to agree with Bogdan, it is standards complying but really 
> > > annoying.
> > > I receive email from 10 - 15 lists and this one is the only one not 
> > > altering the subject.
> > 
> > The recommended way is to use List-Id, To, and Cc.
> > 
> > In Thunderbird, for instance, this is very easy to get via
> > 
> > Tools --> Message Filters
> > 
> > Then match "List-Id contains discuss-gnuradio.gnu.org" and move emails
> > to a separate directory.
> > 
> > Your 10-15 other mailing lists will likely already provide a proper
> > List-Id for many years. Consider that they have the same problem with
> > DKIP and, maybe, switch to (the standard complying) use of List-Id in
> > the future, too.
> > 
> > Cheers,
> > nicolas
> > 


smime.p7s
Description: S/MIME cryptographic signature

Re: gr-gsm make issue with osmosdr module

[Kyeong Su Shin]

Hello Martin,

Does your gr-osmosdr installation work? Maybe you can test that out by creating 
and running a simple flowgraph with a Osmocom Source connected to a QT GUI Sink.

If that fails, then you must have a broken installation of gr-osmosdr and need 
to correct that.  Maybe Python files are installed on a PATH that is not 
recognized by your Python installation (that's actually a pretty common issue). 
If your flowgraph runs, then somehow the Python scripts used by gr-gsm are not 
importing it correctly, and that must be checked.

Regards,
Kyeong Su Shin

보낸 사람: Martin Spears  대신 Discuss-gnuradio 

보낸 날짜: 2019년 11월 20일 수요일 오전 12:21
받는 사람: discuss-gnuradio@gnu.org 
제목: gr-gsm make issue with osmosdr module

I am trying to make gr-gsm I do believe I have all the nessesary support 
libraries:

using :

https://osmocom.org/projects/gr-gsm/wiki/Installation
Installation - gr-gsm - Open Source Mobile 
Communications
Installation¶ There are many ways to install gr-gsm: . Manual compilation and 
installation; Installation from distribution's packages; Compilation and 
installation with use of Pybombs installation manager
osmocom.org
as my starting point.
cmake output

~/src/gr-gsm/build$ cmake ../
-- The CXX compiler identification is GNU 7.4.0
-- The C compiler identification is GNU 7.4.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Build type not specified: defaulting to release.
-- Found LOG4CPP: /usr/lib/x86_64-linux-gnu/liblog4cpp.so
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.1")
-- Checking for module 'gmp'
--   No package 'gmp' found
-- Found GMP: /usr/lib/x86_64-linux-gnu/libgmpxx.so
-- Checking for module 'mpir >= 3.0'
--   No package 'mpir' found
-- Could NOT find MPIR (missing: MPIRXX_LIBRARY MPIR_LIBRARY MPIR_INCLUDE_DIR)
-- Found MPLIB: /usr/lib/x86_64-linux-gnu/libgmpxx.so
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Boost version: 1.65.1
-- Found the following Boost libraries:
--   date_time
--   program_options
--   filesystem
--   system
--   regex
--   thread
--   unit_test_framework
--   chrono
--   atomic
-- Found VOLK: Volk::volk
-- User set python executable /usr/bin/python3
-- Found PythonInterp: /usr/bin/python3 (found version "3.6.8")
-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython3.6m.so (found suitable 
exact version "3.6.8")
-- Checking for module 'fftw3f >= 3.0'
--   Found fftw3f , version 3.3.7
-- Found FFTW3f: /usr/lib/x86_64-linux-gnu/libfftw3f.so
-- Found Git: /usr/bin/git
-- Extracting version information from git describe...
-- Found Doxygen: /usr/bin/doxygen (found version "1.8.13") found components:  
doxygen dot
-- Checking for module 'libosmocore'
--   Found libosmocore, version 1.2.0.65-d0e8
-- Found libosmocore: /usr/local/lib/libosmocore.so
-- Checking for module 'libosmocodec'
--   Found libosmocodec, version 1.2.0.65-d0e8
-- Found libosmocodec: /usr/local/lib/libosmocodec.so
-- Checking for module 'libosmocoding'
--   Found libosmocoding, version 1.2.0.65-d0e8
-- Found libosmocoding: /usr/local/lib/libosmocoding.so
-- Checking for module 'libosmogsm'
--   Found libosmogsm, version 1.2.0.65-d0e8
-- Found libosmogsm: /usr/local/lib/libosmogsm.so
-- Loading build date Tue, 19 Nov 2019 15:07:50 into constants...
-- Loading version v0.41.1-346-g2efaa49e into constants...
-- Using install prefix: /usr/local
-- Building for version: v0.41.1-346-g2efaa49e / 1.0.0git
-- No C++ unit tests... skipping
--
-- Checking for module SWIG
-- Found SWIG version 3.0.12.
-- Found SWIG: /usr/bin/swig3.0
-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython3.6m.so (found version 
"3.6.8")
-- Configuring done
-- Generating done
-- Build files have been written to: /home/martin/src/gr-gsm/build


make output:
[ 73%] Generating grgsm_livemon
<<< Welcome to GNU Radio Companion Compiler 3.8.0.0 >>>

Block paths:
/home/martin/.grc_gnuradio
/home/martin/src/gr-gsm/grc
/usr/share/gnuradio/grc/blocks
/usr/local/share/gnuradio/grc/blocks

>>> Loading: /home/martin/src/gr-gsm/apps/grgsm_livemon.grc
Traceback (most recent call last):
  File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
from .device import *
  File "/home

Re: gr-gsm make issue with osmosdr module

[Martin Spears]

Kyeong Su Shin

purged and re-installed gr-osmosdr from ubuntu package

http://archive.ubuntu.mirror.rafal.ca/ubuntu bionic/universe amd64 gr-osmosdr 
amd64 0.1.4-14build1

[ 71%] Linking CXX shared module _grgsm_swig.so
[ 71%] Built target grgsm_swig
[ 73%] Generating grgsm_livemon
<<< Welcome to GNU Radio Companion Compiler 3.8.0.0 >>>

Block paths:
/home/martin/.grc_gnuradio
/home/martin/src/gr-gsm/grc
/usr/share/gnuradio/grc/blocks
/usr/local/share/gnuradio/grc/blocks

>>> Loading: /home/martin/src/gr-gsm/apps/grgsm_livemon.grc
Traceback (most recent call last):
  File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
from .device import *
  File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, in 

import osmosdr
ModuleNotFoundError: No module named 'osmosdr'
Traceback (most recent call last):
  File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
from .device import *
  File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, in 

import osmosdr
ModuleNotFoundError: No module named 'osmosdr'
Traceback (most recent call last):
  File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
from .device import *
  File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, in 

import osmosdr
ModuleNotFoundError: No module named 'osmosdr'
Traceback (most recent call last):
  File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
from .device import *
  File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, in 

import osmosdr
ModuleNotFoundError: No module named 'osmosdr'
Traceback (most recent call last):
  File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
from .device import *
  File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, in 

import osmosdr
ModuleNotFoundError: No module named 'osmosdr'
Traceback (most recent call last):
  File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
from .device import *
  File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, in 

import osmosdr
ModuleNotFoundError: No module named 'osmosdr'
Traceback (most recent call last):
  File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
from .device import *
  File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, in 

import osmosdr
ModuleNotFoundError: No module named 'osmosdr'
Traceback (most recent call last):
  File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
from .device import *
  File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, in 

import osmosdr
ModuleNotFoundError: No module named 'osmosdr'
Traceback (most recent call last):
  File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
from .device import *
  File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, in 

import osmosdr
ModuleNotFoundError: No module named 'osmosdr'
Traceback (most recent call last):
  File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
from .device import *
  File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, in 

import osmosdr
ModuleNotFoundError: No module named 'osmosdr'
Traceback (most recent call last):
  File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
from .device import *
  File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, in 

import osmosdr
ModuleNotFoundError: No module named 'osmosdr'
Traceback (most recent call last):
  File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
from .device import *
  File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, in 

import osmosdr
ModuleNotFoundError: No module named 'osmosdr'
Traceback (most recent call last):
  File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
from .device import *
  File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, in 

import osmosdr
ModuleNotFoundError: No module named 'osmosdr'
Traceback (most recent call last):
  File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
from .device import *
  File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, in 

import osmosdr
ModuleNotFoundError: No module named 'osmosdr'
Traceback (most recent call last):
  File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
from .device import *
  File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, in 

import osmosdr
ModuleNotFoundError: No module named 'osmosdr'
Traceback (most recent call last):
  File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
from .device import *
  File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, in 

import osmosdr
ModuleNotFou

Re: gr-gsm make issue with osmosdr module

[CEL]

That won't work. The gr-osmosdr you install via apt will be for GNU
Radio 3.7 (which you, by the way, then probably installed as
dependency), and that conflicts with the GNU Radio 3.8 you're using!
On Tue, 2019-11-19 at 16:23 +, Martin Spears wrote:
> Kyeong Su Shin
> 
> purged and re-installed gr-osmosdr from ubuntu package
> 
> http://archive.ubuntu.mirror.rafal.ca/ubuntu bionic/universe amd64 gr-osmosdr 
> amd64 0.1.4-14build1
> 
> [ 71%] Linking CXX shared module _grgsm_swig.so
> [ 71%] Built target grgsm_swig
> [ 73%] Generating grgsm_livemon
> <<< Welcome to GNU Radio Companion Compiler 3.8.0.0 >>>
> 
> Block paths:
> /home/martin/.grc_gnuradio
> /home/martin/src/gr-gsm/grc
> /usr/share/gnuradio/grc/blocks
> /usr/local/share/gnuradio/grc/blocks
> 
> >>> Loading: /home/martin/src/gr-gsm/apps/grgsm_livemon.grc
> Traceback (most recent call last):
>   File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
> 
> from .device import *
>   File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, 
> in 
> import osmosdr
> ModuleNotFoundError: No module named 'osmosdr'
> Traceback (most recent call last):
>   File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
> 
> from .device import *
>   File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, 
> in 
> import osmosdr
> ModuleNotFoundError: No module named 'osmosdr'
> Traceback (most recent call last):
>   File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
> 
> from .device import *
>   File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, 
> in 
> import osmosdr
> ModuleNotFoundError: No module named 'osmosdr'
> Traceback (most recent call last):
>   File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
> 
> from .device import *
>   File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, 
> in 
> import osmosdr
> ModuleNotFoundError: No module named 'osmosdr'
> Traceback (most recent call last):
>   File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
> 
> from .device import *
>   File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, 
> in 
> import osmosdr
> ModuleNotFoundError: No module named 'osmosdr'
> Traceback (most recent call last):
>   File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
> 
> from .device import *
>   File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, 
> in 
> import osmosdr
> ModuleNotFoundError: No module named 'osmosdr'
> Traceback (most recent call last):
>   File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
> 
> from .device import *
>   File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, 
> in 
> import osmosdr
> ModuleNotFoundError: No module named 'osmosdr'
> Traceback (most recent call last):
>   File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
> 
> from .device import *
>   File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, 
> in 
> import osmosdr
> ModuleNotFoundError: No module named 'osmosdr'
> Traceback (most recent call last):
>   File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
> 
> from .device import *
>   File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, 
> in 
> import osmosdr
> ModuleNotFoundError: No module named 'osmosdr'
> Traceback (most recent call last):
>   File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
> 
> from .device import *
>   File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, 
> in 
> import osmosdr
> ModuleNotFoundError: No module named 'osmosdr'
> Traceback (most recent call last):
>   File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
> 
> from .device import *
>   File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, 
> in 
> import osmosdr
> ModuleNotFoundError: No module named 'osmosdr'
> Traceback (most recent call last):
>   File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
> 
> from .device import *
>   File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, 
> in 
> import osmosdr
> ModuleNotFoundError: No module named 'osmosdr'
> Traceback (most recent call last):
>   File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
> 
> from .device import *
>   File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, 
> in 
> import osmosdr
> ModuleNotFoundError: No module named 'osmosdr'
> Traceback (most recent call last):
>   File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
> 
> from .device import *
>   File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, 
> in 
> import osmosdr
> ModuleNotFoundError: No module named 'osmosd

Re: qt-gui problems with GNU 3.8

[Mark Koenig]

So, I opened the docker contained and I did what you suggested (cleaning up 
make and removing the build directory) then successfully rebuilt the gnuradio 
package with the qt-gui module.

What’s odd is that if I try and do this automatically with a dockerfile, using 
the docker build command, I get the qt-gui failures. 

Any thoughts why?

Mark

On 11/19/19, 10:38 AM, "Müller, Marcus   (CEL)"  wrote:

That sounds like `moc` is misbehaving. Or CMake is and the Makefiles
aren't correctly regenerating all necessary files if subsets are
already there.

a) If you haven't, uninstall all potentially half-installed GNU Radios
(don't ask), purge your build folder and cmake; make -j8 again
b) If that doesn't solve it, we'll need to look at the paths: Do the
paths (starting with __ in your, I presume censored, email) look right?

Best regards,
Marcus

On Tue, 2019-11-19 at 15:31 +, Mark Koenig wrote:
> Marcus,
> 
> Here is some feedback regarding using the rpms you helped me create.
> 
> I can run ‘cmake’ with no errors, but running ‘make’ I see the errors 
below with respect to the qt-gui package.  Any advice on how to fix this 
problem?
> 
> Thank you
> 
> Mark
> 
> #38 2179. [ 79%] Generating 
__/include/gnuradio/qtgui/moc_spectrumdisplayform.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 79%] Generating __/include/gnuradio/qtgui/moc_displayform.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 79%] Generating 
__/include/gnuradio/qtgui/moc_timedisplayform.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 79%] Generating 
__/include/gnuradio/qtgui/moc_timecontrolpanel.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 79%] Generating 
__/include/gnuradio/qtgui/moc_timerasterdisplayform.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 79%] Generating 
__/include/gnuradio/qtgui/moc_freqdisplayform.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 79%] Generating 
__/include/gnuradio/qtgui/moc_freqcontrolpanel.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 79%] Generating 
__/include/gnuradio/qtgui/moc_constellationdisplayform.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 80%] Generating 
__/include/gnuradio/qtgui/moc_waterfalldisplayform.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 80%] Generating 
__/include/gnuradio/qtgui/moc_histogramdisplayform.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 80%] Generating 
__/include/gnuradio/qtgui/moc_numberdisplayform.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 80%] Generating 
__/include/gnuradio/qtgui/moc_vectordisplayform.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 80%] Generating __/include/gnuradio/qtgui/moc_form_menus.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 80%] Generating __/include/gnuradio/qtgui/moc_DisplayPlot.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 80%] Generating 
__/include/gnuradio/qtgui/moc_FrequencyDisplayPlot.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 80%] Generating 
__/include/gnuradio/qtgui/moc_TimeDomainDisplayPlot.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 80%] Generating 
__/include/gnuradio/qtgui/moc_TimeRasterDisplayPlot.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 80%] Generating 
__/include/gnuradio/qtgui/moc_WaterfallDisplayPlot.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 80%] Generating 
__/include/gnuradio/qtgui/moc_ConstellationDisplayPlot.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 81%] Generating 
__/include/gnuradio/qtgui/moc_HistogramDisplayPlot.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 81%] Generating 
__/include/gnuradio/qtgui/moc_VectorDisplayPlot.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [

Re: gr-gsm make issue with osmosdr module

[Vasil Velichkov]

Hi Martin,

On 19/11/2019 17.21, Martin Spears wrote:
> I am trying to make gr-gsm I do believe I have all the nessesary support 
> libraries:
> 
> using :
> 
> https://osmocom.org/projects/gr-gsm/wiki/Installation
> Installation - gr-gsm - Open Source Mobile 
> Communications
> Installation¶ There are many ways to install gr-gsm: . Manual compilation and 
> installation; Installation from distribution's packages; Compilation and 
> installation with use of Pybombs installation manager
> osmocom.org
> as my starting point.
> make output:
> [ 73%] Generating grgsm_livemon
> <<< Welcome to GNU Radio Companion Compiler 3.8.0.0 >>>

So you are using gnuradio 3.8, how did you installed it - manually, pybombs or 
from the gnuradio's PPA?
Which gr-gsm version are you trying to compile and from which git 
repository/branch?

The gr-gsm's master branch still does not support gnuradio 3.8. We are working 
on porting it in https://github.com/ptrkrysik/gr-gsm/issues/475
For now you need to checkout and build the `maint-3.8` branch from my fork - 
https://github.com/velichkov/gr-gsm/tree/maint-3.8

> Block paths:
> /home/martin/.grc_gnuradio
> /home/martin/src/gr-gsm/grc
> /usr/share/gnuradio/grc/blocks
> /usr/local/share/gnuradio/grc/blocks
> 
 Loading: /home/martin/src/gr-gsm/apps/grgsm_livemon.grc
> Traceback (most recent call last):
>   File "/home/martin/src/gr-gsm/python/grgsm/__init__.py", line 64, in 
> 
> from .device import *
>   File "/home/martin/src/gr-gsm/python/grgsm/misc_utils/device.py", line 24, 
> in 
> import osmosdr
> ModuleNotFoundError: No module named 'osmosdr'

How did you install gr-osmosdr?

Note that gr-osmosdr from the bionic's apt repository does not support gnuradio 
3.8 so you need to install it manually from one of the forks - 
https://github.com/igorauad/gr-osmosdr/tree/gr3.8 Also note that having 
multiple versions (one from the apt repo in /usr and second one installed 
manually in /usr/local) could lead to many hard to investigate problems. So if 
you want to use gnuradio 3.8 my advice is to remove all gnuradio and gr-osmosdr 
packages installed from the bionic's apt repository.

The manual installation of gr-omosdr will place it's python files in 
/usr/local/lib/python3/dist-packages/ and this path is not in the default 
search paths so you w need to add it to your PYTHONPATH

export PYTHONPATH=/usr/local/lib/python3/dist-packages/:$PYTHONPATH

See also https://github.com/ptrkrysik/gr-gsm/issues/480

P.S.
In the future you may post gr-gsm related questions to the gr-gsm's mailing 
list as well https://github.com/ptrkrysik/gr-gsm/#mailing-list

Regards,
Vasil

Re: qt-gui problems with GNU 3.8

[Vasil Velichkov]

On 19/11/2019 18.46, Mark Koenig wrote:
> So, I opened the docker contained and I did what you suggested (cleaning up 
> make and removing the build directory) then successfully rebuilt the gnuradio 
> package with the qt-gui module.
> 
> What’s odd is that if I try and do this automatically with a dockerfile, 
> using the docker build command, I get the qt-gui failures. 
> 
> Any thoughts why?

Docker has a cache try building with "docker build --no-cache " and if it 
still does not work then provide your Dockerfile.

Re: [Discuss-gnuradio] PyBOMBS documentation recommendations

[Barry Duggan]

I have pushed my latest (final?) revision of the PyBOMBS README.md to 
https://github.com/duggabe/pybombs#pybombs


I will appreciate all comments, suggestions, and technical corrections 
from the community.


---
Barry Duggan KV4FV

RE: Gnuradio for Raspberry PI 4 and SDRPLay works well, but need documentation

[Getz, Robin]

On Friday, November 15, 2019 1:22 PM , Glen I Langston wrote:
[snip]
> I’ve not yet fully checked the SDRPlay for short term transients.
>
>Note that the Pluto SDR has no (or at least few) short term transients in the 
>RF.
> I did find the AIRSPY did have some transients that seem to be due to the 
> device.
> These occur a few thousand times a day, but for shorter than 100 micro 
> seconds.
> Total time on is less than a second a day.
> 

Glen:

I would be interested in what you mean by this. I assume it's mostly "anomalous 
data", and while it's "not right", you aren't sure if it is coming from the RF 
(air interference) or via some transport scheme issue.

If you have a bursty/intermittent adjacent channel (where adjacent can be 
within ~200 MHz of your LO, depending on your hardware), it could cause 
anomalous reception. (This highly depends on your external filters, and 
shielding)...

If you have bursty/intermittent data on harmonics of the LO (again, depending 
on your hardware, external filters, shielding, etc), it could cause anomalous 
reception.

If you have a ground loop, and someone next door turns on their electric drill 
(for example) - this could cause what appear to be receiver problems. (remember 
- you are pulling out signals at -100dBm, into 50 ohms, that is 6.324 µV(p-p) 
or 0.12648 µA(p-p)/ That is pretty tiny, and can be effected by lots of issues.

On AD936x based radios (Pluto, B200, E310, BladeRF 2.0 micro) there is the 
ability to set the Rx to an LFSR/PRBS (Pseudo-Random Bit Sequence), to verify 
"data", which I have run for ~ week with no lost/bad data, both at max rate 
(61.44 MSPS, checking in local in the FPGA), and lower over the various 
transport layers (~5 MSPS over USB and Ethernet), checking in a C application. 
I haven't done it in awhile - and have not gone all the way up to GNU Radio, 
but should be able to pretty easily ... More info at:
https://ez.analog.com/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-20/AD9361BISTFAQ.pdf

If you think you are seeing bad digital/transport data on Pluto - let us know 
so we can track things down. (it's been awhile since we tested this, and 
changes have been made, I will add this to the release test)
Any sort of anomalous device or transport issues - we can try to help look 
into. If they are anomalous RF issues - that's harder. 😊
Our goal is zero device issues all the time - the transport to any application 
should be rock solid.

Let me know.

-Robin

Also - if you are interested in only Rx (like I'm assuming), make sure to turn 
the Tx off.
https://wiki.analog.com/university/tools/pluto/hacking/listening_to_yourself

Re: qt-gui problems with GNU 3.8

[Mark Koenig]

On more additional package, I noticed that does not currently exist the CentOS 
8 repo is ‘log4cpp’.  This package is required by GNU and how I am currently 
handling it is downloading the 
log4cpp-1.1.3.tar.gz file and manually installing the package.  This looks like 
it is working thus far.

Mark

On 11/19/19, 10:38 AM, "Müller, Marcus   (CEL)"  wrote:

That sounds like `moc` is misbehaving. Or CMake is and the Makefiles
aren't correctly regenerating all necessary files if subsets are
already there.

a) If you haven't, uninstall all potentially half-installed GNU Radios
(don't ask), purge your build folder and cmake; make -j8 again
b) If that doesn't solve it, we'll need to look at the paths: Do the
paths (starting with __ in your, I presume censored, email) look right?

Best regards,
Marcus

On Tue, 2019-11-19 at 15:31 +, Mark Koenig wrote:
> Marcus,
> 
> Here is some feedback regarding using the rpms you helped me create.
> 
> I can run ‘cmake’ with no errors, but running ‘make’ I see the errors 
below with respect to the qt-gui package.  Any advice on how to fix this 
problem?
> 
> Thank you
> 
> Mark
> 
> #38 2179. [ 79%] Generating 
__/include/gnuradio/qtgui/moc_spectrumdisplayform.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 79%] Generating __/include/gnuradio/qtgui/moc_displayform.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 79%] Generating 
__/include/gnuradio/qtgui/moc_timedisplayform.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 79%] Generating 
__/include/gnuradio/qtgui/moc_timecontrolpanel.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 79%] Generating 
__/include/gnuradio/qtgui/moc_timerasterdisplayform.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 79%] Generating 
__/include/gnuradio/qtgui/moc_freqdisplayform.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 79%] Generating 
__/include/gnuradio/qtgui/moc_freqcontrolpanel.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 79%] Generating 
__/include/gnuradio/qtgui/moc_constellationdisplayform.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 80%] Generating 
__/include/gnuradio/qtgui/moc_waterfalldisplayform.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 80%] Generating 
__/include/gnuradio/qtgui/moc_histogramdisplayform.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 80%] Generating 
__/include/gnuradio/qtgui/moc_numberdisplayform.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 80%] Generating 
__/include/gnuradio/qtgui/moc_vectordisplayform.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 80%] Generating __/include/gnuradio/qtgui/moc_form_menus.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 80%] Generating __/include/gnuradio/qtgui/moc_DisplayPlot.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 80%] Generating 
__/include/gnuradio/qtgui/moc_FrequencyDisplayPlot.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 80%] Generating 
__/include/gnuradio/qtgui/moc_TimeDomainDisplayPlot.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 80%] Generating 
__/include/gnuradio/qtgui/moc_TimeRasterDisplayPlot.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 80%] Generating 
__/include/gnuradio/qtgui/moc_WaterfallDisplayPlot.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 80%] Generating 
__/include/gnuradio/qtgui/moc_ConstellationDisplayPlot.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 81%] Generating 
__/include/gnuradio/qtgui/moc_HistogramDisplayPlot.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 81%] Generating 
__/include/gnuradio/qtgui/moc_VectorDisplayPlot.cpp
> #38 2179. standard input:0: Note: No relevant classes found. No output 
generated.
> #38 2179. [ 81%] Generating moc_edit_box_msg_impl.cpp

Re: Gnuradio for Raspberry PI 4 and SDRPLay works well, but need documentation

[Glen Langston]

Hi Robin,

When using the AIRSPY (and mini) this summer I was finding some flashes in the 
RF band that
were on for a few 100 micro-seconds, then off.  (The plots are on my home 
computer so I’ll
have to send these on Friday).   The fraction of time the flashes are on is 
very small, less
than a total of one second in 24 hours.  

The spectra from the AIRSPY look very good and the AIRSPY is very reliable in 
sending all
data at the 10 MHz bandwidth (20 MHz I+Q samples).   I could see these 
transients
even when my horns were pointing at the ground, so were not likely due to 
internal sources.

However since my project is looking for transient events, the flashes are an 
issue
for me, but would not be noticed at all by most users.

The PlutoSdr does not seem to be generating many (any?) transients internally, 
which is very 
good. Ie when I point the horns at the ground I get very few/no transients 
appear above 5 sigma, compared
to the noise level.
  
The spectra from the PlutoSDR look good, and I can use a wide range of 
bandwidths, but for bandwidths 
larger than 3.2 MHz I don’t get all the data captured (I know this by 
calculating how long 
I should have to wait for all N samples at a given data rate, and measure the 
actual time it takes 
to get N samples.

The PlutoSDR does not seem to be reliable sending data at rates faster than 3.2 
MHz bandwidth 
(6.4 MHz I+Q samples).  I think it is sending blocks of data on USB but then 
not sending for a while while the data 
are buffered in some part of the USB processing.  The PlutoSDR code in GNuradio 
does not generate the 
Overflow or Underflow letters that other software generates for other devices.  
So the rate issues
are probably not noticed by other users of gnuradio-companion.

I’m working on a version of the Gnuradio code that does not generate any plots 
and
could run entirely internally on the PlutoSDR.  This might be able to capture 
all events
at the full 56 MHz sample rate.

The current code is obtainable by 
git clone http://www.github.com/WVURAIL/gr-radio_astro
This requires some building and compiling.   It works for me on the Raspberry 
Pi 4 and Odroid N2 (Both with 4GB).

I’ve downloaded and installed some else’s PlutoSDR .dfu 
files, that did run gnuradio on the Pluto.  That was working well but I could 
not figure
out how to modify it to build my own c++ libraries.   I might try again.

Regards

Glen


> On Nov 19, 2019, at 2:55 PM, Getz, Robin  wrote:
> 
> On Friday, November 15, 2019 1:22 PM , Glen I Langston wrote:
> [snip]
>> I’ve not yet fully checked the SDRPlay for short term transients.
>> 
>> Note that the Pluto SDR has no (or at least few) short term transients in 
>> the RF.
>> I did find the AIRSPY did have some transients that seem to be due to the 
>> device.
>> These occur a few thousand times a day, but for shorter than 100 micro 
>> seconds.
>> Total time on is less than a second a day.
>> 
> 
> Glen:
> 
> I would be interested in what you mean by this. I assume it's mostly 
> "anomalous data", and while it's "not right", you aren't sure if it is coming 
> from the RF (air interference) or via some transport scheme issue.
> 
> If you have a bursty/intermittent adjacent channel (where adjacent can be 
> within ~200 MHz of your LO, depending on your hardware), it could cause 
> anomalous reception. (This highly depends on your external filters, and 
> shielding)...
> 
> If you have bursty/intermittent data on harmonics of the LO (again, depending 
> on your hardware, external filters, shielding, etc), it could cause anomalous 
> reception.
> 
> If you have a ground loop, and someone next door turns on their electric 
> drill (for example) - this could cause what appear to be receiver problems. 
> (remember - you are pulling out signals at -100dBm, into 50 ohms, that is 
> 6.324 µV(p-p) or 0.12648 µA(p-p)/ That is pretty tiny, and can be effected by 
> lots of issues.
> 
> On AD936x based radios (Pluto, B200, E310, BladeRF 2.0 micro) there is the 
> ability to set the Rx to an LFSR/PRBS (Pseudo-Random Bit Sequence), to verify 
> "data", which I have run for ~ week with no lost/bad data, both at max rate 
> (61.44 MSPS, checking in local in the FPGA), and lower over the various 
> transport layers (~5 MSPS over USB and Ethernet), checking in a C 
> application. I haven't done it in awhile - and have not gone all the way up 
> to GNU Radio, but should be able to pretty easily ... More info at:
> https://ez.analog.com/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-20/AD9361BISTFAQ.pdf
> 
> If you think you are seeing bad digital/transport data on Pluto - let us know 
> so we can track things down. (it's been awhile since we tested this, and 
> changes have been made, I will add this to the release test)
> Any sort of anomalous device or transport issues - we can try to help look 
> into. If they are anomalous RF issues - that's harder. 😊
> Our goal is zero device issues all the time - the transport to any 

gr-radar: ported to GNU Radio 3.8

[Nicolas Cuervo Benavides]

Hi all,

I've been recently working on porting gr-radar to work to GNU Radio 3.8.
These changes can be found in my fork here:
https://github.com/primercuervo/gr-radar

If you'd like to play around with it, please checkout the "maint-3.8"
branch and install in on top of a working GNU Radio 3.8.

I've limited my scope for testing this to the UnitTest available and the
simulation flowgraphs (which are in itself extensive and provide a lot of
coverage). However, I have no hardware to test the over-the-air part of
this OOT, so this is still lacking. All the flowgraphs, regardless of their
HW usage, have been ported to yml as well.

In the meantime, I'll prepare a PR to the main repo. Any type of feedback
is welcome!

Cheers,
-Nico