Re: Struggling with 3.10 OOT Module Porting: AttributeError: module has no attribute
Hi Luca, On 09/09/2022 10.58, Bachmaier, Luca wrote: > Dear all, > > I'm currently porting some of my modules from GNU Radio 3.8 to 3.10 and > experiencing issues with (probably) pybind. My system setup is: Debian 11, > GNU Radio 3.10.3.0. > > My flow graphs that include the 3.8 modules are able to compile, but are not > able to run due to the following error: > File "home/user/.grc_gnuradio/myModule_sync.py", line 56 in > __init__ > Self.myModule_myblock_0 = myModule.myblock(0, 0) > AttributeError: module 'myModule' has no attribute 'myblock' Open `python/__init__.py`, check if there is `except ImportError:` and replace it with `except ModuleNotFoundError:`, then reinstall and try again. See also https://github.com/gnuradio/gnuradio/issues/3884 Regards, Vasil
Re: S Meter
On Fri, 9 Sep 2022 11:36:53 +0100 "R.P. Merrell" wrote: > Hi all > > I am looking for a way to implement a display of the signal strength being > received and have tried various methods using the available blocks in my GNU > 3.10 installation to achieve without success, is their anyone out there who > has successfully done that who could point me in the right direction, > please. > > Many thanks > > Richard G4GUJ. I have used a Qt GUI Number Sink block for this purpose although it has the rather disconcerting property of providing textual output as well as a sliding scale, which can't be switched off. You obviously need to take the block's input before your AGC block (if any) and because it comprises a linear display use logarithmic compression and/or some other form of compression on that input in order to get meaningful results as a signal strength monitor.
Re: [VOLK] Release 2.5.2
On Fri, 9 Sep 2022 11:35:26 +0200 Johannes Demel wrote: > Hi Chris, > > The issue arises in an odd combination. > > 1. you installed VOLK (and cpu_features) to your custom prefix before > 2. your custom prefix is currently NOT sourced > 3. you try to re-compile with `CMAKE_INSTALL_PREFIX=` > > What I've learned so far: > 1. It requires special configuration in a submodule to disable installation. > 2. CMake tries to be smart and the linker does smth different. > > A more complete analysis and a subsequent fix may be nice. > > Cheers > Johannes > > On 08.09.22 23:40, Chris Vine wrote: > > On Sun, 4 Sep 2022 18:41:18 +0200 > > Johannes Demel wrote: > >> Hi everyone! > >> > >> We have a new VOLK release! We are happy to announce VOLK v2.5.2! We > >> want to thank all contributors. This release wouldn't have been possible > >> without them. > > > > Something seems to be amiss when compiling against the internal version > > of cpu_features: > > > >... > >[ 88%] Built target volk_obj > >[ 89%] Linking C shared library libvolk.so > >/usr/bin/ld: cannot find -lcpu_features: No such file or directory > >collect2: error: ld returned 1 exit status > >make[2]: *** [lib/CMakeFiles/volk.dir/build.make:168: > > lib/libvolk.so.2.5.2] Error 1 > >make[1]: *** [CMakeFiles/Makefile2:239: lib/CMakeFiles/volk.dir/all] > > Error 2 > >make: *** [Makefile:146: all] Error 2 Yes I have volk (and gnuradio) installed in a custom prefix. I think you have identified at least part of the problem: volk-2.5.2 compiles correctly if I uninstall the old version of volk (volk-2.5.0) _before_ compiling the new one. The good news is that this seems to be caused by a fairly recent change in volk's build system: volk-2.5.0 compiles fine with a previous version installed - I have just done some test compiles and the build problem seems to have first arisen with volk-2.5.1.
S Meter
Hi all I am looking for a way to implement a display of the signal strength being received and have tried various methods using the available blocks in my GNU 3.10 installation to achieve without success, is their anyone out there who has successfully done that who could point me in the right direction, please. Many thanks Richard G4GUJ.
Re: [VOLK] Release 2.5.2
Hi Chris, The issue arises in an odd combination. 1. you installed VOLK (and cpu_features) to your custom prefix before 2. your custom prefix is currently NOT sourced 3. you try to re-compile with `CMAKE_INSTALL_PREFIX=` What I've learned so far: 1. It requires special configuration in a submodule to disable installation. 2. CMake tries to be smart and the linker does smth different. A more complete analysis and a subsequent fix may be nice. Cheers Johannes On 08.09.22 23:40, Chris Vine wrote: On Sun, 4 Sep 2022 18:41:18 +0200 Johannes Demel wrote: Hi everyone! We have a new VOLK release! We are happy to announce VOLK v2.5.2! We want to thank all contributors. This release wouldn't have been possible without them. Something seems to be amiss when compiling against the internal version of cpu_features: ... [ 88%] Built target volk_obj [ 89%] Linking C shared library libvolk.so /usr/bin/ld: cannot find -lcpu_features: No such file or directory collect2: error: ld returned 1 exit status make[2]: *** [lib/CMakeFiles/volk.dir/build.make:168: lib/libvolk.so.2.5.2] Error 1 make[1]: *** [CMakeFiles/Makefile2:239: lib/CMakeFiles/volk.dir/all] Error 2 make: *** [Makefile:146: all] Error 2 smime.p7s Description: S/MIME Cryptographic Signature
Struggling with 3.10 OOT Module Porting: AttributeError: module has no attribute
Dear all, I'm currently porting some of my modules from GNU Radio 3.8 to 3.10 and experiencing issues with (probably) pybind. My system setup is: Debian 11, GNU Radio 3.10.3.0. My flow graphs that include the 3.8 modules are able to compile, but are not able to run due to the following error: File "home/user/.grc_gnuradio/myModule_sync.py", line 56 in __init__ Self.myModule_myblock_0 = myModule.myblock(0, 0) AttributeError: module 'myModule' has no attribute 'myblock' So far I've checked * That all CMakeFiles.txt in my module folder are similar to the ones that are generated with gr_modtool from 3.10 * That gr-myModule/python/myModule/bindings/python_bindings.cc contains this function call: bind_myblock(m); Calling import myModule and dir(myModule) in Python returns the following: ['__builtins__', '__cached__', '__doc__', '__file__', '__loader__', '__name__', '__package__', '__path__', '__spec__', 'os', 'myModule_python'] Calling dir(myModule.myModule_python) prints this: ['__doc__', '__file__', '__loader__', '__name__', '__package__', '__spec__'] Comparing the call dir(myModule) to my setup with GNU Radio 3.8, all of my custom blocks should be listed. I would be very happy if someone could help me. Thanks in advance and regards, Luca
