Re: Teething problems with new GNU Radio 3.9 installation

[David Scaperoth]

Brendan,

Out of curiosity, what versions of tensorflow and cuda are you using?

David

On Thu, Apr 22, 2021, 12:50 AM Brendan Horsfield <
brendan.horsfi...@vectalabs.com> wrote:

> Hi Ryan,
>
> I have some good news to report.
>
> While I was waiting for your reply (the curse of living Down Under), I
> tried installing the UHD / GNU Radio combo you mentioned in your last
> email, namely:
>
>- UHD 3.15 (with Python bindings)
>- GR 3.8.3 (actually maint-3.8, which installed
>as v3.8.2.0-112-ge20ffa3c)
>
> Both were installed from source, without using a conda environment.  I
> fired up gnuradio-companion at the end, and bingo, I'm back in business!
> No errors, no warnings, old flowgraphs still working.
>
> Thanks for your help in getting me back on track -- I was starting to lose
> hope!
>
> Regards,
> Brendan.
>
>
>
> On Thu, Apr 22, 2021 at 2:05 PM Ryan Volz  wrote:
>
>> Hi Brendan,
>>
>> On April 21, 2021 7:14:41 PM EDT, Brendan Horsfield <
>> brendan.horsfi...@vectalabs.com> wrote:
>> >Hi Ryan,
>> >
>> >Thanks, that sounds like a MUCH easier way of doing things!
>> >
>> >A couple of questions:
>> >
>> >- I don't have much experience with virtual environments.  If I install
>> > one of your packages into a conda environment, will I still be able to
>> >   access applications & libraries that were installed outside of conda
>> >   (specifically Python, TensorFlow, CUDA & Docker)?  Or will I have to
>> > reinstall those resources inside the same conda environment as the GNU
>> >   Radio package?
>>
>> Everything would have to be installed into the conda environment,
>> assuming you want to use them in the same Python process. (You could
>> probably get tricky with PYTHONPATH or something, but I sure wouldn't
>> recommend it.) Tensorflow and CUDA stuff could be a little tough, because
>> currently that requires mixing the conda-forge channel
>> (community-supported, where uhd and gnuradio are) and the defaults channel
>> (provided by Anaconda Inc., where tensorflow-gpu is available). Depending
>> on how you install conda, you'll want to make sure you also have the
>> defaults channel available at a lower priority than conda-forge:
>>
>> conda config --append channels defaults
>>
>> Then
>>
>> conda install tensorflow-gpu
>>
>> should work to get you everything (assuming you have the NVIDIA driver
>> installed normally). It would be good to double-check my instructions by
>> consulting some guides, e.g.:
>>
>> https://docs.anaconda.com/anaconda/user-guide/tasks/tensorflow/
>>
>> Assuming you mentioned Docker only as a way to get tensorflow set up with
>> GPU support, then you shouldn't need it. Hopefully tensorflow-gpu will make
>> it to conda-forge soon (the infrastructure needed to do the build has only
>> recently been set up, and pytorch-gpu was added just today), and then
>> installation will get even easier.
>>
>> >  - Slightly off-topic, but still related:  As mentioned in my original
>> >post, I have already installed UHD & GNU Radio from source on my
>> >system.
>> >This was not done inside a virtual environment.  If I now want to
>> >uninstall
>> >those items, is it as simple as going into their respective "build"
>> >folders
>> >(e.g. ~/workarea-gnuradio/gnuradio/build) and running "sudo make
>> >uninstall"
>> >   and "sudo make clean"?  Or is there more to it than that?
>>
>> That should clean up all of the installed files (the make uninstall part,
>> clean would not be necessary), but configuration files and cache files
>> would still remain. It's almost certainly not necessary to uninstall your
>> other build while trying/using the conda one as I've never experienced
>> interference of that flavor. What could cause trouble are the config/cache
>> files that would remain either way. But now you know about that possibility
>> and know to clean those out if there are any problems. Just make sure to
>> activate your conda environment and you'll be good to go.
>>
>> >
>> >Thanks,
>> >Brendan.
>> >
>>
>> Cheers,
>> Ryan
>>
>

Re: Why does preferences file get installed in /usr/local despite setting custom install prefix?

[Cinaed Simson]

On 4/21/21 9:48 PM, wan wrote:

Hi all,

I set a custom install prefix while installing from source. However, 
the preference file still gets installed to /usr/local, as you can see 
from the gnuradio-config-info output below.


gnuradio-config-info --print-all
/home/.../envs/uhd-gr-default/
/home/.../envs/uhd-gr-default/etc
/usr/local/etc/gnuradio/conf.d
/home/.../.gnuradio

Why does preferences file get installed in /usr/local despite setting 
a custom install prefix? And is this expected?


Regards,

Wan L.


Hi Wan - you should indicate the version of gnuradio you installed.

Something appears to have gone wrong with your install - you're missing 
most of the expected information. It looks like your home directory was


  /home/..

For comparison,  here's  the output for version 3.8 that I installed 
from source.


gnuradio-config-info --print-all
/opt/gnuradio
/opt/gnuradio/etc
/opt/gnuradio/etc/gnuradio/conf.d
/home/cinaed/.gnuradio

testing-support;python-support;volk;doxygen;sphinx;gnuradio-runtime;gr-ctrlport;gnuradio-companion;gr-blocks;gr-fec;gr-fft;gr-filter;gr-analog;gr-digital;gr-dtv;gr-audio;* 
alsa;* oss;* jack;* 
portaudio;gr-channels;gr-qtgui;gr-trellis;gr-uhd;gr-utils;gr_modtool;gr-video-sdl;gr-vocoder;* 
gsm;gr-wavelet;gr-zeromq

v3.8.2.0-73-g4a84443c
gcc (Debian 8.3.0-6) 8.3.0
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software see the source for copying conditions.  There is NO
warranty not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
g++ (Debian 8.3.0-6) 8.3.0
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software see the source for copying conditions.  There is NO
warranty not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
/usr/bin/gcc:::-O3 -DNDEBUG -march=native -O3 -fvisibility=hidden 
-Wsign-compare -Wall -Wno-uninitialized
/usr/bin/g++:::-O3 -DNDEBUG -march=native -O3 -fvisibility=hidden 
-Wsign-compare -Wall -Wno-uninitialized

FFT MARKER

[Alberto Alletto]

Hi!
There is a mode to make an Marker on FFT signal as spectrum analyzer 
instruments ?

Alberto
Inviato da iPhone

Re: Teething problems with new GNU Radio 3.9 installation

[Brendan Horsfield]

Hi David,

My current configuration is as follows:

   - TensorFlow 2.4.1
   - CUDA 11.2

I am also running a second version of TensorFlow inside a Docker image that
I downloaded from dockerhub:

   -
   
https://hub.docker.com/r/tensorflow/tensorflow/tags?page=1=last_updated

My preferred image is "tensorflow:latest-gpu", but you will see that there
are many, many others to choose from, depending on what combination of
libraries you want.

The Docker version of TensorFlow is usually much easier to install, as it
comes equipped with all of the necessary dependencies (including CUDA
drivers).  The only downside is that the image I am using ("latest-gpu")
doesn't support graphical tools like Matplotlib, which means you can only
print results to the console as simple text.  This makes it great for model
training, but not so good for model testing or inference, where you often
want to visualise your model's performance with colourful plots.

Regards,
Brendan.




On Thu, 22 Apr 2021, 20:24 David Scaperoth, 
wrote:

> Brendan,
>
> Out of curiosity, what versions of tensorflow and cuda are you using?
>
> David
>
> On Thu, Apr 22, 2021, 12:50 AM Brendan Horsfield <
> brendan.horsfi...@vectalabs.com> wrote:
>
>> Hi Ryan,
>>
>> I have some good news to report.
>>
>> While I was waiting for your reply (the curse of living Down Under), I
>> tried installing the UHD / GNU Radio combo you mentioned in your last
>> email, namely:
>>
>>- UHD 3.15 (with Python bindings)
>>- GR 3.8.3 (actually maint-3.8, which installed
>>as v3.8.2.0-112-ge20ffa3c)
>>
>> Both were installed from source, without using a conda environment.  I
>> fired up gnuradio-companion at the end, and bingo, I'm back in business!
>> No errors, no warnings, old flowgraphs still working.
>>
>> Thanks for your help in getting me back on track -- I was starting to
>> lose hope!
>>
>> Regards,
>> Brendan.
>>
>>
>>
>> On Thu, Apr 22, 2021 at 2:05 PM Ryan Volz  wrote:
>>
>>> Hi Brendan,
>>>
>>> On April 21, 2021 7:14:41 PM EDT, Brendan Horsfield <
>>> brendan.horsfi...@vectalabs.com> wrote:
>>> >Hi Ryan,
>>> >
>>> >Thanks, that sounds like a MUCH easier way of doing things!
>>> >
>>> >A couple of questions:
>>> >
>>> >- I don't have much experience with virtual environments.  If I install
>>> > one of your packages into a conda environment, will I still be able to
>>> >   access applications & libraries that were installed outside of conda
>>> >   (specifically Python, TensorFlow, CUDA & Docker)?  Or will I have to
>>> > reinstall those resources inside the same conda environment as the GNU
>>> >   Radio package?
>>>
>>> Everything would have to be installed into the conda environment,
>>> assuming you want to use them in the same Python process. (You could
>>> probably get tricky with PYTHONPATH or something, but I sure wouldn't
>>> recommend it.) Tensorflow and CUDA stuff could be a little tough, because
>>> currently that requires mixing the conda-forge channel
>>> (community-supported, where uhd and gnuradio are) and the defaults channel
>>> (provided by Anaconda Inc., where tensorflow-gpu is available). Depending
>>> on how you install conda, you'll want to make sure you also have the
>>> defaults channel available at a lower priority than conda-forge:
>>>
>>> conda config --append channels defaults
>>>
>>> Then
>>>
>>> conda install tensorflow-gpu
>>>
>>> should work to get you everything (assuming you have the NVIDIA driver
>>> installed normally). It would be good to double-check my instructions by
>>> consulting some guides, e.g.:
>>>
>>> https://docs.anaconda.com/anaconda/user-guide/tasks/tensorflow/
>>>
>>> Assuming you mentioned Docker only as a way to get tensorflow set up
>>> with GPU support, then you shouldn't need it. Hopefully tensorflow-gpu will
>>> make it to conda-forge soon (the infrastructure needed to do the build has
>>> only recently been set up, and pytorch-gpu was added just today), and then
>>> installation will get even easier.
>>>
>>> >  - Slightly off-topic, but still related:  As mentioned in my original
>>> >post, I have already installed UHD & GNU Radio from source on my
>>> >system.
>>> >This was not done inside a virtual environment.  If I now want to
>>> >uninstall
>>> >those items, is it as simple as going into their respective "build"
>>> >folders
>>> >(e.g. ~/workarea-gnuradio/gnuradio/build) and running "sudo make
>>> >uninstall"
>>> >   and "sudo make clean"?  Or is there more to it than that?
>>>
>>> That should clean up all of the installed files (the make uninstall
>>> part, clean would not be necessary), but configuration files and cache
>>> files would still remain. It's almost certainly not necessary to uninstall
>>> your other build while trying/using the conda one as I've never experienced
>>> interference of that flavor. What could cause trouble are the config/cache
>>> files that would remain either way. But now you know about that possibility
>>> and know to clean those out if there are any 

Re: Why does preferences file get installed in /usr/local despite setting custom install prefix?

[Neel Pandeya]

Hello Wan:

Did you set a custom installation path when you ran CMake?

How did you invoke CMake when you built GNU Radio?

The Application Note listed below might help you.

https://kb.ettus.com/Building_and_Installing_UHD_and_GNU_Radio_to_a_Custom_Prefix

--Neel Pandeya



On Thu, 22 Apr 2021 at 02:28, Cinaed Simson  wrote:

>
> On 4/21/21 9:48 PM, wan wrote:
> > Hi all,
> >
> > I set a custom install prefix while installing from source. However,
> > the preference file still gets installed to /usr/local, as you can see
> > from the gnuradio-config-info output below.
> >
> > gnuradio-config-info --print-all
> > /home/.../envs/uhd-gr-default/
> > /home/.../envs/uhd-gr-default/etc
> > /usr/local/etc/gnuradio/conf.d
> > /home/.../.gnuradio
> >
> > Why does preferences file get installed in /usr/local despite setting
> > a custom install prefix? And is this expected?
> >
> > Regards,
> >
> > Wan L.
>
> Hi Wan - you should indicate the version of gnuradio you installed.
>
> Something appears to have gone wrong with your install - you're missing
> most of the expected information. It looks like your home directory was
>
>/home/..
>
> For comparison,  here's  the output for version 3.8 that I installed
> from source.
>
> gnuradio-config-info --print-all
> /opt/gnuradio
> /opt/gnuradio/etc
> /opt/gnuradio/etc/gnuradio/conf.d
> /home/cinaed/.gnuradio
>
> testing-support;python-support;volk;doxygen;sphinx;gnuradio-runtime;gr-ctrlport;gnuradio-companion;gr-blocks;gr-fec;gr-fft;gr-filter;gr-analog;gr-digital;gr-dtv;gr-audio;*
>
> alsa;* oss;* jack;*
> portaudio;gr-channels;gr-qtgui;gr-trellis;gr-uhd;gr-utils;gr_modtool;gr-video-sdl;gr-vocoder;*
>
> gsm;gr-wavelet;gr-zeromq
> v3.8.2.0-73-g4a84443c
> gcc (Debian 8.3.0-6) 8.3.0
> Copyright (C) 2018 Free Software Foundation, Inc.
> This is free software see the source for copying conditions.  There is NO
> warranty not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> g++ (Debian 8.3.0-6) 8.3.0
> Copyright (C) 2018 Free Software Foundation, Inc.
> This is free software see the source for copying conditions.  There is NO
> warranty not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> /usr/bin/gcc:::-O3 -DNDEBUG -march=native -O3 -fvisibility=hidden
> -Wsign-compare -Wall -Wno-uninitialized
> /usr/bin/g++:::-O3 -DNDEBUG -march=native -O3 -fvisibility=hidden
> -Wsign-compare -Wall -Wno-uninitialized
>
>
>

Re: Why does preferences file get installed in /usr/local despite setting custom install prefix?

[wan]

Hi Cinaed and Neel,

Thanks for your quick response.

My custom prefix is /home/. I was just shortening it with
"/home/...", sorry for the confusion.

I followed a similar process as in the app note.
I ran $ cmake-gui ../ in the build directory.
Then I used the GUI to configure and generate the flags
CMAKE_INSTALL_PREFIX, UHD_DIR, UHD_INCLUDE_DIRS, and UHD_LIBRARIES. I also
set PYTHON_EXECUTABLE to usr/bin/python3.8

For good measure, tried to build again, this time I can ran
$ cmake -DCMAKE_INSTALL_PREFIX=/home/ -DUHD_DIR=/home//lib/cmake/uhd -DUHD_INCLUDE_DIRS=/home//include
-DUHD_LIBRARIES = /home//lib/libuhd.so
-DPYTHON_EXECUTABLE=/usr/bin/python3.8 ../

The preferences file is still installed to /usr/local

Here's the full gnuradio-config-info output after second attempt

/home/
/home//etc
/usr/local/etc/gnuradio/conf.d
/home//.gnuradio
Thu, 22 Apr 2021 15:25:41
testing-support;python-support;post-install;doxygen;gnuradio-runtime;gr-ctrlport
3.9.0.0
cc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software see the source for copying conditions.  There is NO
warranty not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
c++ (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software see the source for copying conditions.  There is NO
warranty not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
/usr/bin/cc:::-O3 -DNDEBUG  -fvisibility=hidden -Wsign-compare -Wall
-Wno-uninitialized
/usr/bin/c++:::-O3 -DNDEBUG  -fvisibility=hidden -Wsign-compare -Wall
-Wno-uninitialized


On Thu, 22 Apr 2021 at 08:31, Neel Pandeya  wrote:
>
> Hello Wan:
>
> Did you set a custom installation path when you ran CMake?
>
> How did you invoke CMake when you built GNU Radio?
>
> The Application Note listed below might help you.
>
>
https://kb.ettus.com/Building_and_Installing_UHD_and_GNU_Radio_to_a_Custom_Prefix
>
> --Neel Pandeya
>
>
>
> On Thu, 22 Apr 2021 at 02:28, Cinaed Simson 
wrote:
>>
>>
>> On 4/21/21 9:48 PM, wan wrote:
>> > Hi all,
>> >
>> > I set a custom install prefix while installing from source. However,
>> > the preference file still gets installed to /usr/local, as you can see
>> > from the gnuradio-config-info output below.
>> >
>> > gnuradio-config-info --print-all
>> > /home/.../envs/uhd-gr-default/
>> > /home/.../envs/uhd-gr-default/etc
>> > /usr/local/etc/gnuradio/conf.d
>> > /home/.../.gnuradio
>> >
>> > Why does preferences file get installed in /usr/local despite setting
>> > a custom install prefix? And is this expected?
>> >
>> > Regards,
>> >
>> > Wan L.
>>
>> Hi Wan - you should indicate the version of gnuradio you installed.
>>
>> Something appears to have gone wrong with your install - you're missing
>> most of the expected information. It looks like your home directory was
>>
>>/home/..
>>
>> For comparison,  here's  the output for version 3.8 that I installed
>> from source.
>>
>> gnuradio-config-info --print-all
>> /opt/gnuradio
>> /opt/gnuradio/etc
>> /opt/gnuradio/etc/gnuradio/conf.d
>> /home/cinaed/.gnuradio
>>
>>
testing-support;python-support;volk;doxygen;sphinx;gnuradio-runtime;gr-ctrlport;gnuradio-companion;gr-blocks;gr-fec;gr-fft;gr-filter;gr-analog;gr-digital;gr-dtv;gr-audio;*
>> alsa;* oss;* jack;*
>>
portaudio;gr-channels;gr-qtgui;gr-trellis;gr-uhd;gr-utils;gr_modtool;gr-video-sdl;gr-vocoder;*
>> gsm;gr-wavelet;gr-zeromq
>> v3.8.2.0-73-g4a84443c
>> gcc (Debian 8.3.0-6) 8.3.0
>> Copyright (C) 2018 Free Software Foundation, Inc.
>> This is free software see the source for copying conditions.  There is NO
>> warranty not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.
>> g++ (Debian 8.3.0-6) 8.3.0
>> Copyright (C) 2018 Free Software Foundation, Inc.
>> This is free software see the source for copying conditions.  There is NO
>> warranty not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.
>> /usr/bin/gcc:::-O3 -DNDEBUG -march=native -O3 -fvisibility=hidden
>> -Wsign-compare -Wall -Wno-uninitialized
>> /usr/bin/g++:::-O3 -DNDEBUG -march=native -O3 -fvisibility=hidden
>> -Wsign-compare -Wall -Wno-uninitialized
>>
>>

GNU Radio 3.9 OOT derived class

[Alvaro Pendas Recondo]

Hello,

I am trying to implement my own header class derived from
'header_format_default' named 'header_format_counter_dif'. As you can
imagine, the class is quite similar to 'header_format_counter' with some
minor adjustments. My situation is almost identical to the one presented in
this mailing list before
https://lists.gnu.org/archive/html/discuss-gnuradio/2017-04/msg00063.html

However, the difference is that I am using GNU Radio 3.9, so in my case the
steps I have taken are

*Steps taken so far:*
1. Created my new module *TFMv3 *with gr_modtool
2. Added *header_format_counter_dif* (c++) using gr_modtool as type
'noblock'
3. Fleshed out the .cc and .h files based on the class
'header_format_counter' (but with some changes).
4. Made sure to *#include * in
the header file
5. Used *digital::header_format_default* as the parent class in the class
declaration since it's now in separate namespace to 'digital'
6. Add the line set(GR_REQUIRED_COMPONENTS RUNTIME DIGITAL) at
gr-TFMv3/CMakeLists.txt
6. Add the line py::module::import("gnuradio.digital") at python_bindings.cc

After that, I run *gr_modtool bind header_format_counter_dif *and I am able
to compile successfully. However, when importing TFMv3 I get the error
*undefined
symbol: _ZTIN2gr7digital21header_format_defaultE* which stand for *typeinfo
for gr::digital::header_format_default* (I found out using a C++ name
demangler).


So it seems I am missing something when including the mother class
correctly. Any ideas about what it might be?

Than you very much,

Álvaro

Re: GNU Radio 3.9 OOT derived class

[Vasil Velichkov]

Hi Alvaro,

On 22/04/2021 17.48, Alvaro Pendas Recondo wrote:
> 6. Add the line set(GR_REQUIRED_COMPONENTS RUNTIME DIGITAL) at
> gr-TFMv3/CMakeLists.txt

The GR_REQUIRED_COMPONENTS is no longer used in GNU Radio 3.8 and 3.9. You need 
to add "digital" in the Gnuradio's find_package list and then link your OOT 
module with gnuradio::gnuradio-digital. It should be something similar to:

find_package(Gnuradio "3.8" REQUIRED COMPONENTS digital)
target_link_libraries(gnuradio-TFMv3 gnuradio::gnuradio-digital)

See 
https://wiki.gnuradio.org/index.php/GNU_Radio_3.8_OOT_Module_Porting_Guide#GNU_Radio_Components

Regards,
Vasil

Re: GNU Radio 3.9 OOT derived class

[Alvaro Pendas Recondo]

Hi Vasil,

Thank you for your answer. Should not be Gnuradio "3.9" instead of "3.9"?.
Anyway, I tried with both options and I got the same error:

Target "TFMv3_python" links to target "gnuradio::gnuradio-digital" but the
  target was not found.  Perhaps a find_package() call is missing for an
  IMPORTED target, or an ALIAS target is missing?

What I changed was:

1 - Write *find_package(Gnuradio "3.9" REQUIRED COMPONENTS digital filter
blocks analog fft)* in CMakeLists.txt
2 - Write t*arget_link_libraries(gnuradio-TFMv3 gnuradio::gnuradio-runtime
gnuradio::gnuradio-digital*
*gnuradio::gnuradio-blocks gnuradio::gnuradio-filter
gnuradio::gnuradio-analog gnuradio::gnuradio-fft) *in lib/CMakeLists.txt

As I've said, I tried with both "3.8" and "3.9" with the same output. I had
to add filter blocks analog and fft as expected based on the explanation
https://wiki.gnuradio.org/index.php/GNU_Radio_3.8_OOT_Module_Porting_Guide#GNU_Radio_Components



El jue, 22 abr 2021 a las 17:13, Vasil Velichkov ()
escribió:

> Hi Alvaro,
>
> On 22/04/2021 17.48, Alvaro Pendas Recondo wrote:
> > 6. Add the line set(GR_REQUIRED_COMPONENTS RUNTIME DIGITAL) at
> > gr-TFMv3/CMakeLists.txt
>
> The GR_REQUIRED_COMPONENTS is no longer used in GNU Radio 3.8 and 3.9. You
> need to add "digital" in the Gnuradio's find_package list and then link
> your OOT module with gnuradio::gnuradio-digital. It should be something
> similar to:
>
> find_package(Gnuradio "3.8" REQUIRED COMPONENTS digital)
> target_link_libraries(gnuradio-TFMv3 gnuradio::gnuradio-digital)
>
> See
> https://wiki.gnuradio.org/index.php/GNU_Radio_3.8_OOT_Module_Porting_Guide#GNU_Radio_Components
>
> Regards,
> Vasil
>

Re: GNU Radio 3.9 OOT derived class

[Vasil Velichkov]

Hi Alvaro,

On 22/04/2021 19.02, Alvaro Pendas Recondo wrote:
> Thank you for your answer. Should not be Gnuradio "3.9" instead of "3.9"?.

Yes, use the version you are developing for.

> Anyway, I tried with both options and I got the same error:
> 
> Target "TFMv3_python" links to target "gnuradio::gnuradio-digital" but the
>   target was not found.  Perhaps a find_package() call is missing for an
>   IMPORTED target, or an ALIAS target is missing?

Try deleting the build directory (or at least delete CMakeCache.txt file), 
re-run cmake again and provide the full output.

Can you share the whole source code? As a github repo for example.

Regards,
Vasil

Re: Why does preferences file get installed in /usr/local despite setting custom install prefix?

[Cinaed Simson]

Hi Wan - this path

  /home/..

is not your home path - or your home directory.

Type

  cd /home/..

and then

  ls

and see if you find the gnuradio directory. If you didn't have root 
privilege at the time then the install failed.


Assuming your userid is

  wan

then

  /home/wan

is you home directory..

What operating system and version are your running?

-- Cinaed


On 4/22/21 8:56 AM, wan wrote:

Hi Cinaed and Neel,

Thanks for your quick response.

My custom prefix is /home/. I was just shortening it with 
"/home/...", sorry for the confusion.


I followed a similar process as in the app note.
I ran $ cmake-gui ../ in the build directory.
Then I used the GUI to configure and generate the flags 
CMAKE_INSTALL_PREFIX, UHD_DIR, UHD_INCLUDE_DIRS, and UHD_LIBRARIES. I 
also set PYTHON_EXECUTABLE to usr/bin/python3.8


For good measure, tried to build again, this time I can ran
$ cmake -DCMAKE_INSTALL_PREFIX=/home/ -DUHD_DIR=/home/path>/lib/cmake/uhd -DUHD_INCLUDE_DIRS=/home//include 
-DUHD_LIBRARIES = /home//lib/libuhd.so 
-DPYTHON_EXECUTABLE=/usr/bin/python3.8 ../


The preferences file is still installed to /usr/local

Here's the full gnuradio-config-info output after second attempt

/home/
/home//etc
/usr/local/etc/gnuradio/conf.d
/home//.gnuradio
Thu, 22 Apr 2021 15:25:41
testing-support;python-support;post-install;doxygen;gnuradio-runtime;gr-ctrlport
3.9.0.0
cc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software see the source for copying conditions. There is NO
warranty not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
c++ (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software see the source for copying conditions. There is NO
warranty not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
/usr/bin/cc:::-O3 -DNDEBUG  -fvisibility=hidden -Wsign-compare -Wall 
-Wno-uninitialized
/usr/bin/c++:::-O3 -DNDEBUG  -fvisibility=hidden -Wsign-compare -Wall 
-Wno-uninitialized



On Thu, 22 Apr 2021 at 08:31, Neel Pandeya > wrote:

>
> Hello Wan:
>
> Did you set a custom installation path when you ran CMake?
>
> How did you invoke CMake when you built GNU Radio?
>
> The Application Note listed below might help you.
>
> 
https://kb.ettus.com/Building_and_Installing_UHD_and_GNU_Radio_to_a_Custom_Prefix 


>
> --Neel Pandeya
>
>
>
> On Thu, 22 Apr 2021 at 02:28, Cinaed Simson > wrote:

>>
>>
>> On 4/21/21 9:48 PM, wan wrote:
>> > Hi all,
>> >
>> > I set a custom install prefix while installing from source. However,
>> > the preference file still gets installed to /usr/local, as you 
can see

>> > from the gnuradio-config-info output below.
>> >
>> > gnuradio-config-info --print-all
>> > /home/.../envs/uhd-gr-default/
>> > /home/.../envs/uhd-gr-default/etc
>> > /usr/local/etc/gnuradio/conf.d
>> > /home/.../.gnuradio
>> >
>> > Why does preferences file get installed in /usr/local despite setting
>> > a custom install prefix? And is this expected?
>> >
>> > Regards,
>> >
>> > Wan L.
>>
>> Hi Wan - you should indicate the version of gnuradio you installed.
>>
>> Something appears to have gone wrong with your install - you're missing
>> most of the expected information. It looks like your home directory was
>>
>>    /home/..
>>
>> For comparison,  here's  the output for version 3.8 that I installed
>> from source.
>>
>> gnuradio-config-info --print-all
>> /opt/gnuradio
>> /opt/gnuradio/etc
>> /opt/gnuradio/etc/gnuradio/conf.d
>> /home/cinaed/.gnuradio
>>
>> 
testing-support;python-support;volk;doxygen;sphinx;gnuradio-runtime;gr-ctrlport;gnuradio-companion;gr-blocks;gr-fec;gr-fft;gr-filter;gr-analog;gr-digital;gr-dtv;gr-audio;*

>> alsa;* oss;* jack;*
>> 
portaudio;gr-channels;gr-qtgui;gr-trellis;gr-uhd;gr-utils;gr_modtool;gr-video-sdl;gr-vocoder;*

>> gsm;gr-wavelet;gr-zeromq
>> v3.8.2.0-73-g4a84443c
>> gcc (Debian 8.3.0-6) 8.3.0
>> Copyright (C) 2018 Free Software Foundation, Inc.
>> This is free software see the source for copying conditions.  There 
is NO
>> warranty not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR 
PURPOSE.

>> g++ (Debian 8.3.0-6) 8.3.0
>> Copyright (C) 2018 Free Software Foundation, Inc.
>> This is free software see the source for copying conditions.  There 
is NO
>> warranty not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR 
PURPOSE.

>> /usr/bin/gcc:::-O3 -DNDEBUG -march=native -O3 -fvisibility=hidden
>> -Wsign-compare -Wall -Wno-uninitialized
>> /usr/bin/g++:::-O3 -DNDEBUG -march=native -O3 -fvisibility=hidden
>> -Wsign-compare -Wall -Wno-uninitialized
>>
>>

Re: Windows 7 x64 problem...

[Alberto]

No idea ? 



Inviato da iPhone

> Il giorno 19 apr 2021, alle ore 17:55, Alberto  
> ha scritto:
> 
> Hi !
> I have created a simple example to View 100MHz signal from sdr receiver...but 
> i have a problem.
> 
> My OS is Windows 7 x64, GNURadio 3.7.13.5.
> 
> When i start a receiver with gnuradio an window error open:
> 
> Pyton.exe has stop working
> 
> Can you help me ?
> 
> Alberto
> 
> 
> 
> 
> Inviato da iPhone

Re: GNU Radio 3.9 OOT derived class

[Alvaro Pendas Recondo]

I've tried with no result. The full output is

-- The CXX compiler identification is GNU 9.3.0
-- The C compiler identification is GNU 9.3.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 PkgConfig: /usr/bin/pkg-config (found version "0.29.1")
-- Found LOG4CPP: /usr/lib/x86_64-linux-gnu/liblog4cpp.so
-- Checking for module 'gmp'
--   Found gmp, version 6.2.0
-- 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
-- Found Boost:
/usr/lib/x86_64-linux-gnu/cmake/Boost-1.71.0/BoostConfig.cmake (found
suitable version "1.71.0", minimum required is "1.71.0") found components:
date_time program_options filesystem system regex thread
unit_test_framework
-- Found Volk: Volk::volk
-- User set python executable /usr/bin/python3
-- Found PythonInterp: /usr/bin/python3 (found version "3.8.5")
-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython3.8.so (found
suitable exact version "3.8.5")
-- Found Git: /usr/bin/git
-- Found Doxygen: /usr/bin/doxygen (found version "1.8.17") found
components: doxygen missing components: dot
-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython3.8.so
-- Using install prefix: /usr/local
-- Building for version: v1.0-compat-xxx-xunknown / 1.0.0git
-- No C++ unit tests... skipping
-- PYTHON and GRC components are enabled
-- Python checking for pygccxml - found
-- Performing Test HAS_FLTO
-- Performing Test HAS_FLTO - Success
-- LTO enabled
-- Checking for module 'mpir >= 3.0'
--   No package 'mpir' found
-- Could NOT find MPIR (missing: MPIRXX_LIBRARY MPIR_LIBRARY
MPIR_INCLUDE_DIR)
-- Checking for module 'sndfile'
--   Found sndfile, version 1.0.28
-- Found SNDFILE: /usr/lib/x86_64-linux-gnu/libsndfile.so
-- Checking for module 'fftw3f >= 3.0'
--   Found fftw3f , version 3.3.8
-- Found FFTW3f: /usr/lib/x86_64-linux-gnu/libfftw3f.so
-- Configuring done
CMake Error at /usr/local/share/cmake/pybind11/pybind11Tools.cmake:131
(add_library):
  Target "TFMv3_python" links to target "gnuradio::gnuradio-digital" but the
  target was not found.  Perhaps a find_package() call is missing for an
  IMPORTED target, or an ALIAS target is missing?
Call Stack (most recent call first):
  /usr/local/lib/cmake/gnuradio/GrPybind.cmake:243 (pybind11_add_module)
  python/bindings/CMakeLists.txt:34 (GR_PYBIND_MAKE_OOT)


CMake Error at /usr/local/share/cmake/pybind11/pybind11Tools.cmake:131
(add_library):
  Target "TFMv3_python" links to target "gnuradio::gnuradio-analog" but the
  target was not found.  Perhaps a find_package() call is missing for an
  IMPORTED target, or an ALIAS target is missing?
Call Stack (most recent call first):
  /usr/local/lib/cmake/gnuradio/GrPybind.cmake:243 (pybind11_add_module)
  python/bindings/CMakeLists.txt:34 (GR_PYBIND_MAKE_OOT)


CMake Error at /usr/local/share/cmake/pybind11/pybind11Tools.cmake:131
(add_library):
  Target "TFMv3_python" links to target "gnuradio::gnuradio-blocks" but the
  target was not found.  Perhaps a find_package() call is missing for an
  IMPORTED target, or an ALIAS target is missing?
Call Stack (most recent call first):
  /usr/local/lib/cmake/gnuradio/GrPybind.cmake:243 (pybind11_add_module)
  python/bindings/CMakeLists.txt:34 (GR_PYBIND_MAKE_OOT)


CMake Error at /usr/local/share/cmake/pybind11/pybind11Tools.cmake:131
(add_library):
  Target "TFMv3_python" links to target "gnuradio::gnuradio-fft" but the
  target was not found.  Perhaps a find_package() call is missing for an
  IMPORTED target, or an ALIAS target is missing?
Call Stack (most recent call first):
  /usr/local/lib/cmake/gnuradio/GrPybind.cmake:243 (pybind11_add_module)
  python/bindings/CMakeLists.txt:34 (GR_PYBIND_MAKE_OOT)


CMake Error at /usr/local/share/cmake/pybind11/pybind11Tools.cmake:131
(add_library):
  Target "TFMv3_python" links to target "gnuradio::gnuradio-filter" but the
  target was not found.  Perhaps a find_package() call is missing for an
  IMPORTED target, or an ALIAS target is missing?
Call Stack (most recent call first):
  /usr/local/lib/cmake/gnuradio/GrPybind.cmake:243 (pybind11_add_module)
  python/bindings/CMakeLists.txt:34 (GR_PYBIND_MAKE_OOT)


CMake Error at /usr/local/share/cmake/pybind11/pybind11Tools.cmake:131
(add_library):
  Target "TFMv3_python" links to target "gnuradio::gnuradio-digital" but the
  target was not found.  Perhaps a find_package() 

Re: GNU Radio 3.9 OOT derived class

[Jeff Long]

I'd suggest starting over with modtool. There are a number of directories
in your code that should not be there (e.g., gnuradio-runtime, gr-fec,
gr-fft, gr-blocks, ...). Something went wrong in the process of getting all
this set up.

On Thu, Apr 22, 2021 at 7:45 PM Alvaro Pendas Recondo 
wrote:

> I've tried with no result. The full output is
>
> -- The CXX compiler identification is GNU 9.3.0
> -- The C compiler identification is GNU 9.3.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 PkgConfig: /usr/bin/pkg-config (found version "0.29.1")
> -- Found LOG4CPP: /usr/lib/x86_64-linux-gnu/liblog4cpp.so
> -- Checking for module 'gmp'
> --   Found gmp, version 6.2.0
> -- 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
> -- Found Boost:
> /usr/lib/x86_64-linux-gnu/cmake/Boost-1.71.0/BoostConfig.cmake (found
> suitable version "1.71.0", minimum required is "1.71.0") found components:
> date_time program_options filesystem system regex thread
> unit_test_framework
> -- Found Volk: Volk::volk
> -- User set python executable /usr/bin/python3
> -- Found PythonInterp: /usr/bin/python3 (found version "3.8.5")
> -- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython3.8.so (found
> suitable exact version "3.8.5")
> -- Found Git: /usr/bin/git
> -- Found Doxygen: /usr/bin/doxygen (found version "1.8.17") found
> components: doxygen missing components: dot
> -- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython3.8.so
> -- Using install prefix: /usr/local
> -- Building for version: v1.0-compat-xxx-xunknown / 1.0.0git
> -- No C++ unit tests... skipping
> -- PYTHON and GRC components are enabled
> -- Python checking for pygccxml - found
> -- Performing Test HAS_FLTO
> -- Performing Test HAS_FLTO - Success
> -- LTO enabled
> -- Checking for module 'mpir >= 3.0'
> --   No package 'mpir' found
> -- Could NOT find MPIR (missing: MPIRXX_LIBRARY MPIR_LIBRARY
> MPIR_INCLUDE_DIR)
> -- Checking for module 'sndfile'
> --   Found sndfile, version 1.0.28
> -- Found SNDFILE: /usr/lib/x86_64-linux-gnu/libsndfile.so
> -- Checking for module 'fftw3f >= 3.0'
> --   Found fftw3f , version 3.3.8
> -- Found FFTW3f: /usr/lib/x86_64-linux-gnu/libfftw3f.so
> -- Configuring done
> CMake Error at /usr/local/share/cmake/pybind11/pybind11Tools.cmake:131
> (add_library):
>   Target "TFMv3_python" links to target "gnuradio::gnuradio-digital" but
> the
>   target was not found.  Perhaps a find_package() call is missing for an
>   IMPORTED target, or an ALIAS target is missing?
> Call Stack (most recent call first):
>   /usr/local/lib/cmake/gnuradio/GrPybind.cmake:243 (pybind11_add_module)
>   python/bindings/CMakeLists.txt:34 (GR_PYBIND_MAKE_OOT)
>
>
> CMake Error at /usr/local/share/cmake/pybind11/pybind11Tools.cmake:131
> (add_library):
>   Target "TFMv3_python" links to target "gnuradio::gnuradio-analog" but the
>   target was not found.  Perhaps a find_package() call is missing for an
>   IMPORTED target, or an ALIAS target is missing?
> Call Stack (most recent call first):
>   /usr/local/lib/cmake/gnuradio/GrPybind.cmake:243 (pybind11_add_module)
>   python/bindings/CMakeLists.txt:34 (GR_PYBIND_MAKE_OOT)
>
>
> CMake Error at /usr/local/share/cmake/pybind11/pybind11Tools.cmake:131
> (add_library):
>   Target "TFMv3_python" links to target "gnuradio::gnuradio-blocks" but the
>   target was not found.  Perhaps a find_package() call is missing for an
>   IMPORTED target, or an ALIAS target is missing?
> Call Stack (most recent call first):
>   /usr/local/lib/cmake/gnuradio/GrPybind.cmake:243 (pybind11_add_module)
>   python/bindings/CMakeLists.txt:34 (GR_PYBIND_MAKE_OOT)
>
>
> CMake Error at /usr/local/share/cmake/pybind11/pybind11Tools.cmake:131
> (add_library):
>   Target "TFMv3_python" links to target "gnuradio::gnuradio-fft" but the
>   target was not found.  Perhaps a find_package() call is missing for an
>   IMPORTED target, or an ALIAS target is missing?
> Call Stack (most recent call first):
>   /usr/local/lib/cmake/gnuradio/GrPybind.cmake:243 (pybind11_add_module)
>   python/bindings/CMakeLists.txt:34 (GR_PYBIND_MAKE_OOT)
>
>
> CMake Error at /usr/local/share/cmake/pybind11/pybind11Tools.cmake:131
> (add_library):
>   Target "TFMv3_python" links to target "gnuradio::gnuradio-filter" but the
>   target