Re: Help GRC with USRP N300

[Michael Dickens]

Hi Jean Marie - 2 thoughts:

1) Did you run "sudo ldconfig" after installation? Always a good idea to do
that after installing anything, to update to LD cache.

2) If you run
{{{
/usr/bin/python2 -c "import sys; print(sys.path)"
}}}
is one of the paths "/usr/local/lib/python2.7/dist-packages"?  If not, then
you need to add that path to the shell environment PYTHONPATH variable, and
add it to one of the shell login command scripts. For example if you use
BASH, then you could add the following to ~/.bashrc:
{{{
export PYTHONPATH=/usr/local/lib/python2.7/dist-packages:$PYTHONPATH
}}}
so that when you login this path is automatically available. You can, of
course, set it in your current terminal to test / verify that doing so
fixes the issue.

Hope this is useful! - MLD

On Wed, Feb 12, 2020 at 8:43 AM Jean Marie Brieussel 
wrote:

> Hi,
>
> I installed UHD V3.15.0.0 and GNURadio V3.7.13.4 the loaded FPGA image is
> the XG. I checked the correct functioning of UHD and GNURadio as well as
> the USRP N300 with UHD, the tests are correct. I checked that the N300 is
> seen by the host PC, see the result below:
>
> jmf6etu@JM-F6ETU:~$ uhd_find_devices
> [INFO] [UHD] linux; GNU C++ version 7.4.0; Boost_106501;
> UHD_3.15.0.HEAD-0-gaea0e2de
> --
> -- UHD Device 0
> --
> Device Address:
> serial: 31C037E
> addr: 192.168.20.2
> claimed: False
> mgmt_addr: 192.168.10.2
> mgmt_addr: 192.168.20.2
> product: n300
> type: n3xx
> I did the small classic test program under GRC, see the attached
> screenshot, (I hope that the attached files are visible on this discussion
> list).
>
> In copy if below the Terminal information lines:
>
> jmf6etu@JM-F6ETU:~$ gnuradio-companion
> Gtk-Message: 14:15:09.794: Failed to load module "canberra-gtk-module"
> <<< Welcome to GNU Radio Companion 3.7.13.4 >>>
>
> Block paths:
> /usr/local/share/gnuradio/grc/blocks
>
> Loading: "/home/jmf6etu/Bureau/Appli_GNU/FM_exemplegrc.grc"
> >>> Done
>
> Loading: "/home/jmf6etu/Bureau/Appli_GNU/gene.grc"
> >>> Done
>
> Generating: '/home/jmf6etu/Bureau/Appli_GNU/fm_exemple.py'
>
> Executing: /usr/bin/python2 -u
> /home/jmf6etu/Bureau/Appli_GNU/fm_exemple.py
>
> Traceback (most recent call last):
>   File "/home/jmf6etu/Bureau/Appli_GNU/fm_exemple.py", line 25, in
> 
> from gnuradio import uhd
>   File "*/usr/local/lib/python2.7/dist-packages/gnuradio/uhd/*__init__.py",
> line 135, in 
> _prepare_uhd_swig()
>   File "*/usr/local/lib/python2.7/dist-packages/gnuradio/uhd/*__init__.py",
> line 38, in _prepare_uhd_swig
> import uhd_swig
>   File "/usr/local/lib/python2.7/dist-packages/gnuradio/uhd/uhd_swig.py",
> line 17, in 
> _uhd_swig = swig_import_helper()
>   File "/usr/local/lib/python2.7/dist-packages/gnuradio/uhd/uhd_swig.py",
> line 16, in swig_import_helper
> return importlib.import_module('_uhd_swig')
>   File "*/usr/lib/python2.7/importlib/*__init__.py", line 37, in
> import_module
> __import__(name)
> ImportError: No module named _uhd_swig
>
> >>> Done (return code 1)
> Advice to solve my problems is welcome.
>
> Best Regards,
>
> Jean Marie
>


-- 
Michael Dickens
Ettus Research Technical Support
Email: supp...@ettus.com
Web: https://ettus.com/

probe signal gnuradio3.8

[sarandis. Doulgeris]

After installing gnuradio 3.8 i saw that the block probe signal does not
have a Block ID parameter so i cant use the probe function. How can i fix
that?

AttributeError: OOT Modul

[Till Hülder]

Hello,

 

i build a OOT Module and after installing i get this error when i run the program .

 

  File "/home/iheamira/Dokumente/BA_Huelder/gnu-radio/top_block.py", line 219, in 
    main()
  File "/home/iheamira/Dokumente/BA_Huelder/gnu-radio/top_block.py", line 207, in main
    tb = top_block_cls()
  File "/home/iheamira/Dokumente/BA_Huelder/gnu-radio/top_block.py", line 142, in __init__
    self.control_control_b_0 = control.control_b(5e-6, 1000, 10, 5e-6, 5e-6, 5e-6, 200e-6, 100e-6, 0.2, samp_rate)
AttributeError: 'module' object has no attribute 'control_b'

 

How can i fix this?

 

Best regards ,

Til

Re: AttributeError: OOT Modul

[Ivan Iudice]

Hi,
are you under Ubuntu Linux?
Try running first as root “ldconfig”.

Ivan

> Il giorno 12 feb 2020, alle ore 15:46, Till Hülder  ha 
> scritto:
> 
> 
> Hello,
>  
> i build a OOT Module and after installing i get this error when i run the 
> program .
>  
>   File "/home/iheamira/Dokumente/BA_Huelder/gnu-radio/top_block.py", line 
> 219, in 
> main()
>   File "/home/iheamira/Dokumente/BA_Huelder/gnu-radio/top_block.py", line 
> 207, in main
> tb = top_block_cls()
>   File "/home/iheamira/Dokumente/BA_Huelder/gnu-radio/top_block.py", line 
> 142, in __init__
> self.control_control_b_0 = control.control_b(5e-6, 1000, 10, 5e-6, 5e-6, 
> 5e-6, 200e-6, 100e-6, 0.2, samp_rate)
> AttributeError: 'module' object has no attribute 'control_b'
>  
> How can i fix this?
>  
> Best regards ,
> Til

Re: AttributeError: OOT Modul

[Michael Dickens]

Hi Til - Without seeing your code, we can just provide some basic advice,
such as the prior email. If you have a GitHub or GitLab public repo for
this we can take a look ... otherwise it's just guesswork on our end! - MLD

On Wed, Feb 12, 2020 at 9:48 AM "Till Hülder"  wrote:

> Hello,
>
> i build a OOT Module and after installing i get this error when i run the
> program .
>
>   File "/home/iheamira/Dokumente/BA_Huelder/gnu-radio/top_block.py", line
> 219, in 
> main()
>   File "/home/iheamira/Dokumente/BA_Huelder/gnu-radio/top_block.py", line
> 207, in main
> tb = top_block_cls()
>   File "/home/iheamira/Dokumente/BA_Huelder/gnu-radio/top_block.py", line
> 142, in __init__
> self.control_control_b_0 = control.control_b(5e-6, 1000, 10, 5e-6,
> 5e-6, 5e-6, 200e-6, 100e-6, 0.2, samp_rate)
> AttributeError: 'module' object has no attribute 'control_b'
>
> How can i fix this?
>
> Best regards ,
> Til
>


-- 
Michael Dickens
Ettus Research Technical Support
Email: supp...@ettus.com
Web: https://ettus.com/

Error cross-compiling OOT modules for E310

[krono86]

  
Hi guys, 
I'm trying to compile one of mine OOT module (C++), but
I'm obtaining a curious error. 
https://pastebin.com/ZyfJcHCa 
Looking
at warnings, it seems that several header files are got from
/usr/include, and not from sdk sysroot. 
What's going on? 
Thank you.

Ivan  


Con Tiscali Mobile Smart 30 4G hai minuti illimitati, 100 SMS e 30 Giga in 4G a 
soli 8,99€ al mese. http://tisca.li/smart30

Re: AttributeError: OOT Modul

[Vasil Velichkov]

Hi Till,

On 12/02/2020 16.46, "Till Hülder" wrote:
> Hello,
> i build a OOT Module and after installing i get this error when i run the 
> program .
>File "/home/iheamira/Dokumente/BA_Huelder/gnu-radio/top_block.py", line 
> 219, 
> in 
>  main()
>File "/home/iheamira/Dokumente/BA_Huelder/gnu-radio/top_block.py", line 
> 207, 
> in main
>  tb = top_block_cls()
>File "/home/iheamira/Dokumente/BA_Huelder/gnu-radio/top_block.py", line 
> 142, 
> in __init__
>  self.control_control_b_0 = control.control_b(5e-6, 1000, 10, 5e-6, 5e-6, 
> 5e-6, 200e-6, 100e-6, 0.2, samp_rate)
> AttributeError: 'module' object has no attribute 'control_b'

One possible reason for such error is that there are undefined symbols in your 
shared library.

Go to the build directory and execute

ldd -r lib/lib*.so
ldd -r swig/*_swig.so

and if you see "undefined symbol:" messages that means you are not linking all 
dependencies.

Also in `python/__init__.py` you probably have a try except block like this one

  # import swig generated symbols into the OOT namespace
  try:
  # this might fail if the module is python-only
  from .OOT_swig import *
  except ImportError:
  pass

Consider removing the try: and except and keep only the import line

  from .OOT_swig import *

Read also:
https://lists.gnu.org/archive/html/discuss-gnuradio/2020-02/msg00047.html
https://lists.gnu.org/archive/html/discuss-gnuradio/2020-02/msg00054.html

Regards,
Vasil

Re: UPDATE: Re: gnuradio error

[Vasil Velichkov]

Hi Mike,

Please keep the gnuradio mailing list in the loop.

Did you enable the copr repo first or just installed using dnf with an URL to 
the RPM?

Somehow you ended with two different versions installed on the same time. My 
recommendation is to remove gnuradio 3.7 and then reinstall 3.8

  sudo dnf remove gnuradio-3.7.13.5
  sudo dnf reinstall gnuradio-3.8.0.0

Also it seems like you ran gdb after installing 3.8, you needed to run it 
before that.

Regards,
Vasil

On 12/02/2020 15.28, Mike Gilmer wrote:
> Vasil,
> I ran sudo dnf info gnuradio and got this
> ++
> Available Packages
> Name : gnuradio
> Version  : 3.7.13.5
> Release  : 6.fc31
> Architecture : i686
> Size : 13 M
> Source   : gnuradio-3.7.13.5-6.fc31.src.rpm
> Repository   : fedora
> Summary  : Software defined radio framework
> URL  : http://www.gnuradio.org
> License  : GPLv3
> Description  : GNU Radio is a collection of software that when combined with
>  : minimal hardware, allows the construction of radios where the
>  : actual waveforms transmitted and received are defined by
>  : software. What this means is that it turns the digital
> modulation
>  : schemes used in today's high performance wireless devices
> into
>  : software problems.
> 
> Name : gnuradio
> Version  : 3.8.0.0
> Release  : 2.fc31
> Architecture : src
> Size : 2.3 M
> Source   : None
> Repository   : copr:copr.fedorainfracloud.org:gnuradio:gnuradio-releases
> Summary  : Software defined radio framework
> URL  : http://www.gnuradio.org
> License  : GPLv3
> Description  : GNU Radio is a collection of software that when combined with
>  : minimal hardware, allows the construction of radios where the
>  : actual waveforms transmitted and received are defined by
>  : software. What this means is that it turns the digital
> modulation
>  : schemes used in today's high performance wireless devices
> into
>  : software problems.
> 
> 
> ++
> 
> On Wed, Feb 12, 2020 at 8:16 AM Mike Gilmer  wrote:
> 
>> Hi Vasil,
>>
>> Thanks for getting back to me.
>>
>> I installed gnuradio using sudo dnf install and got 3.8?
>> ( About says 3.8.0.0 (Python 3.7.6) )
>> There may be an failed build-from-source gnuradio on this machine?
>>
>>
>> I installed your recommendations and ran the command you suggested and got
>> this:
>> 
>>
>> GNU gdb (GDB) Fedora 8.3.50.20190824-28.fc31
>> Copyright (C) 2019 Free Software Foundation, Inc.
>> License GPLv3+: GNU GPL version 3 or later <
>> http://gnu.org/licenses/gpl.html>
>> This is free software: you are free to change and redistribute it.
>> There is NO WARRANTY, to the extent permitted by law.
>> Type "show copying" and "show warranty" for details.
>> This GDB was configured as "x86_64-redhat-linux-gnu".
>> Type "show configuration" for configuration details.
>> For bug reporting instructions, please see:
>> .
>> Find the GDB manual and other documentation resources online at:
>> .
>>
>> For help, type "help".
>> Type "apropos word" to search for commands related to "word"...
>> Reading symbols from /usr/bin/python2...
>> Reading symbols from .gnu_debugdata for /usr/bin/python2.7...
>> (No debugging symbols found in .gnu_debugdata for /usr/bin/python2.7)
>> Starting program: /usr/bin/python2 /usr/bin/gnuradio-companion
>> [Thread debugging using libthread_db enabled]
>> Using host libthread_db library "/lib64/libthread_db.so.1".
>> ImportError
>>
>> Cannot import gnuradio.
>>
>> Is the model path environment variable set correctly?
>> All OS: PYTHONPATH
>>
>> Is the library path environment variable set correctly?
>> Linux: LD_LIBRARY_PATH
>> Windows: PATH
>> MacOSX: DYLD_LIBRARY_PATH
>>
>>
>> (No module named gnuradio)
>> [Inferior 1 (process 7766) exited with code 01]
>> No stack.
>> Missing separate debuginfos, use: dnf debuginfo-install
>> python2-2.7.17-1.fc31.x86_64
>> (gdb)
>>
>> +
>>
>> Thanks for your help so far.
>> b/r
>> Mike
>>
>> On Tue, Feb 11, 2020 at 3:28 PM Vasil Velichkov 
>> wrote:
>>
>>> Hi Mike,
>>>
>>> On 11/02/2020 21.38, Mike Gilmer wrote:
 I installed gnuradio on  Fedora  5.4.17-200.fc31.x86_64 using sudo dnf
 install gnuradio
>>>
>>> The gnuradio's version in Fedora 31 is 3.7.13.5-6.fc31.x86_64 and
>>> 5.4.17-200 is the version of the Linux kernel.
>>>
>>> You can find the newer version 3.8 in the COPR repository
>>> https://wiki.gnuradio.org/index.php/InstallingGR#Fedora_COPR_Installation
>>>
 Afterwards when I attempt to run gnuradio-companion (typing
 gnuradio-companion in a terminal) I see several e

Re: probe signal gnuradio3.8

[Vasil Velichkov]

Hi Sarandis Doulgeris,

On 12/02/2020 16.28, sarandis. Doulgeris wrote:
> After installing gnuradio 3.8 i saw that the block probe signal does not
> have a Block ID parameter so i cant use the probe function. How can i fix
> that?

This sounds like this[1] issue, it was fixed for some blocks in commit 
0fa281fd73 [2].

A quick solution is to open blocks_probe_signal_x.block.yml and 
blocks_probe_signal_vx.block.yml and add show_id to the flags.

   flags: [ show_id, python, cpp ]

[1] https://github.com/gnuradio/gnuradio/issues/2235
[2] https://github.com/gnuradio/gnuradio/pull/2568 

Thanks for reporting this.

Regards,
Vasil

Version compatibility problem

[Laura Arjona]

Good morning,

In short, I installed gnuradio 3.8 following the tutorial  in the github
site

sudo -H pip3 install PyBOMBS
pybombs auto-config
pybombs recipes add-defaults
pybombs prefix init ~/gnuradio -R gnuradio-default


but I got problems with the python path, then removed gnuradio,  and
re-installed the version 3.7.

But when I check the version with gnuradio-config-info --version
I still get version 3.8.0.

Because of the version I have other eros when building my oot-modules.


Any advice there?

Thanks!


-- 
*Laura Arjona *
Washington Research Foundation Innovation Postdoctoral Fellow in
Neuroengineering

*Paul G. Allen School of Computer Science & Engineering*
185 E Stevens Way NE
University of Washington
Seattle, WA 98195-2350

Re: Version compatibility problem

[CEL]

Hi Laura,

first of all, unless you really want to work *on* GNU Radio, there's
little reason to install it using PyBOMBS. At the very least, on Debian
testing, there's native GNU Radio 3.8 packages, and for Fedora and
Ubuntu, GNU Radio has binary packages that you can just install and use
to develop your out-of-tree modules and GNU Radio applications.

However, PyBOMBS will have installed GNU Radio 3.8 into the prefix
~/gnuradio. So, if you just move that out of the way, or delete it,
then you should have no access to GNU Radio 3.8.0.0 anymore.

Best regards,
Marcus

On Wed, 2020-02-12 at 12:12 -0800, Laura Arjona wrote:
> Good morning,
> 
> In short, I installed gnuradio 3.8 following the tutorial  in the github site
> sudo -H pip3 install PyBOMBS
> pybombs auto-config
> pybombs recipes add-defaults
> pybombs prefix init ~/gnuradio -R gnuradio-default
> 
> but I got problems with the python path, then removed gnuradio,  and 
> re-installed the version 3.7.
> 
> But when I check the version with gnuradio-config-info --version
> I still get version 3.8.0.
> 
> Because of the version I have other eros when building my oot-modules.
> 
> 
> Any advice there? 
> 
> Thanks!
> 
> 


smime.p7s
Description: S/MIME cryptographic signature

Re: Version compatibility problem

[Laura Arjona]

Thank you,

I got rid of all the folders named  gnuradio, and it seems to be
uninstalled, because when  I run uninstall  I get Package 'gnuradio' is not
installed, so not removed

But I still get
#  gnuradio-config-info --version
3.8.0.0



On Wed, Feb 12, 2020 at 12:47 PM Müller, Marcus (CEL) 
wrote:

> Hi Laura,
>
> first of all, unless you really want to work *on* GNU Radio, there's
> little reason to install it using PyBOMBS. At the very least, on Debian
> testing, there's native GNU Radio 3.8 packages, and for Fedora and
> Ubuntu, GNU Radio has binary packages that you can just install and use
> to develop your out-of-tree modules and GNU Radio applications.
>
> However, PyBOMBS will have installed GNU Radio 3.8 into the prefix
> ~/gnuradio. So, if you just move that out of the way, or delete it,
> then you should have no access to GNU Radio 3.8.0.0 anymore.
>
> Best regards,
> Marcus
>
> On Wed, 2020-02-12 at 12:12 -0800, Laura Arjona wrote:
> > Good morning,
> >
> > In short, I installed gnuradio 3.8 following the tutorial  in the github
> site
> > sudo -H pip3 install PyBOMBS
> > pybombs auto-config
> > pybombs recipes add-defaults
> > pybombs prefix init ~/gnuradio -R gnuradio-default
> >
> > but I got problems with the python path, then removed gnuradio,  and
> re-installed the version 3.7.
> >
> > But when I check the version with gnuradio-config-info --version
> > I still get version 3.8.0.
> >
> > Because of the version I have other eros when building my oot-modules.
> >
> >
> > Any advice there?
> >
> > Thanks!
> >
> >
>


-- 
*Laura Arjona *
Washington Research Foundation Innovation Postdoctoral Fellow in
Neuroengineering

*Paul G. Allen School of Computer Science & Engineering*
185 E Stevens Way NE
University of Washington
Seattle, WA 98195-2350

Re: Version compatibility problem

[CEL]

huh. Seems to be more than one installation in the prefix?!
what does `which gnuradio-config-info` say?


On Wed, 2020-02-12 at 13:52 -0800, Laura Arjona wrote:
> Thank you,
> 
> I got rid of all the folders named  gnuradio, and it seems to be
> uninstalled, because when  I run uninstall  I get Package 'gnuradio'
> is not installed, so not removed
> 
> But I still get
> #  gnuradio-config-info --version
> 3.8.0.0
> 
> 
> 
> On Wed, Feb 12, 2020 at 12:47 PM Müller, Marcus (CEL) <
> muel...@kit.edu> wrote:
> > Hi Laura,
> > 
> > first of all, unless you really want to work *on* GNU Radio,
> > there's
> > little reason to install it using PyBOMBS. At the very least, on
> > Debian
> > testing, there's native GNU Radio 3.8 packages, and for Fedora and
> > Ubuntu, GNU Radio has binary packages that you can just install and
> > use
> > to develop your out-of-tree modules and GNU Radio applications.
> > 
> > However, PyBOMBS will have installed GNU Radio 3.8 into the prefix
> > ~/gnuradio. So, if you just move that out of the way, or delete it,
> > then you should have no access to GNU Radio 3.8.0.0 anymore.
> > 
> > Best regards,
> > Marcus
> > 
> > On Wed, 2020-02-12 at 12:12 -0800, Laura Arjona wrote:
> > > Good morning,
> > > 
> > > In short, I installed gnuradio 3.8 following the tutorial  in the
> > github site
> > > sudo -H pip3 install PyBOMBS
> > > pybombs auto-config
> > > pybombs recipes add-defaults
> > > pybombs prefix init ~/gnuradio -R gnuradio-default
> > > 
> > > but I got problems with the python path, then removed gnuradio, 
> > and re-installed the version 3.7.
> > > 
> > > But when I check the version with gnuradio-config-info --version
> > > I still get version 3.8.0.
> > > 
> > > Because of the version I have other eros when building my oot-
> > modules.
> > > 
> > > 
> > > Any advice there? 
> > > 
> > > Thanks!
> > > 
> > > 
> 
> 


smime.p7s
Description: S/MIME cryptographic signature

Re: Version compatibility problem

[Laura Arjona]

Thank you Marcus.

I think I am going to install ubuntu again, since I really  need to have
gnuradio working asap.

It says nothing
~$ which gnradio-config-info

:~$ gnuradio-config-info --version
3.8.0.0

On Wed, Feb 12, 2020 at 2:42 PM Müller, Marcus (CEL) 
wrote:

> huh. Seems to be more than one installation in the prefix?!
> what does `which gnuradio-config-info` say?
>
>
> On Wed, 2020-02-12 at 13:52 -0800, Laura Arjona wrote:
> > Thank you,
> >
> > I got rid of all the folders named  gnuradio, and it seems to be
> > uninstalled, because when  I run uninstall  I get Package 'gnuradio'
> > is not installed, so not removed
> >
> > But I still get
> > #  gnuradio-config-info --version
> > 3.8.0.0
> >
> >
> >
> > On Wed, Feb 12, 2020 at 12:47 PM Müller, Marcus (CEL) <
> > muel...@kit.edu> wrote:
> > > Hi Laura,
> > >
> > > first of all, unless you really want to work *on* GNU Radio,
> > > there's
> > > little reason to install it using PyBOMBS. At the very least, on
> > > Debian
> > > testing, there's native GNU Radio 3.8 packages, and for Fedora and
> > > Ubuntu, GNU Radio has binary packages that you can just install and
> > > use
> > > to develop your out-of-tree modules and GNU Radio applications.
> > >
> > > However, PyBOMBS will have installed GNU Radio 3.8 into the prefix
> > > ~/gnuradio. So, if you just move that out of the way, or delete it,
> > > then you should have no access to GNU Radio 3.8.0.0 anymore.
> > >
> > > Best regards,
> > > Marcus
> > >
> > > On Wed, 2020-02-12 at 12:12 -0800, Laura Arjona wrote:
> > > > Good morning,
> > > >
> > > > In short, I installed gnuradio 3.8 following the tutorial  in the
> > > github site
> > > > sudo -H pip3 install PyBOMBS
> > > > pybombs auto-config
> > > > pybombs recipes add-defaults
> > > > pybombs prefix init ~/gnuradio -R gnuradio-default
> > > >
> > > > but I got problems with the python path, then removed gnuradio,
> > > and re-installed the version 3.7.
> > > >
> > > > But when I check the version with gnuradio-config-info --version
> > > > I still get version 3.8.0.
> > > >
> > > > Because of the version I have other eros when building my oot-
> > > modules.
> > > >
> > > >
> > > > Any advice there?
> > > >
> > > > Thanks!
> > > >
> > > >
> >
> >
>


-- 
*Laura Arjona *
Washington Research Foundation Innovation Postdoctoral Fellow in
Neuroengineering

*Paul G. Allen School of Computer Science & Engineering*
185 E Stevens Way NE
University of Washington
Seattle, WA 98195-2350

Re: Version compatibility problem

[Laura Arjona]

sorry, typed it wrong
~$ which gnradio-config-info
/usr/local/bin/gnuradio-config-info

On Wed, Feb 12, 2020 at 3:03 PM Laura Arjona  wrote:

> Thank you Marcus.
>
> I think I am going to install ubuntu again, since I really  need to have
> gnuradio working asap.
>
> It says nothing
> ~$ which gnradio-config-info
>
> :~$ gnuradio-config-info --version
> 3.8.0.0
>
> On Wed, Feb 12, 2020 at 2:42 PM Müller, Marcus (CEL) 
> wrote:
>
>> huh. Seems to be more than one installation in the prefix?!
>> what does `which gnuradio-config-info` say?
>>
>>
>> On Wed, 2020-02-12 at 13:52 -0800, Laura Arjona wrote:
>> > Thank you,
>> >
>> > I got rid of all the folders named  gnuradio, and it seems to be
>> > uninstalled, because when  I run uninstall  I get Package 'gnuradio'
>> > is not installed, so not removed
>> >
>> > But I still get
>> > #  gnuradio-config-info --version
>> > 3.8.0.0
>> >
>> >
>> >
>> > On Wed, Feb 12, 2020 at 12:47 PM Müller, Marcus (CEL) <
>> > muel...@kit.edu> wrote:
>> > > Hi Laura,
>> > >
>> > > first of all, unless you really want to work *on* GNU Radio,
>> > > there's
>> > > little reason to install it using PyBOMBS. At the very least, on
>> > > Debian
>> > > testing, there's native GNU Radio 3.8 packages, and for Fedora and
>> > > Ubuntu, GNU Radio has binary packages that you can just install and
>> > > use
>> > > to develop your out-of-tree modules and GNU Radio applications.
>> > >
>> > > However, PyBOMBS will have installed GNU Radio 3.8 into the prefix
>> > > ~/gnuradio. So, if you just move that out of the way, or delete it,
>> > > then you should have no access to GNU Radio 3.8.0.0 anymore.
>> > >
>> > > Best regards,
>> > > Marcus
>> > >
>> > > On Wed, 2020-02-12 at 12:12 -0800, Laura Arjona wrote:
>> > > > Good morning,
>> > > >
>> > > > In short, I installed gnuradio 3.8 following the tutorial  in the
>> > > github site
>> > > > sudo -H pip3 install PyBOMBS
>> > > > pybombs auto-config
>> > > > pybombs recipes add-defaults
>> > > > pybombs prefix init ~/gnuradio -R gnuradio-default
>> > > >
>> > > > but I got problems with the python path, then removed gnuradio,
>> > > and re-installed the version 3.7.
>> > > >
>> > > > But when I check the version with gnuradio-config-info --version
>> > > > I still get version 3.8.0.
>> > > >
>> > > > Because of the version I have other eros when building my oot-
>> > > modules.
>> > > >
>> > > >
>> > > > Any advice there?
>> > > >
>> > > > Thanks!
>> > > >
>> > > >
>> >
>> >
>>
>
>
> --
> *Laura Arjona *
> Washington Research Foundation Innovation Postdoctoral Fellow in
> Neuroengineering
>
> *Paul G. Allen School of Computer Science & Engineering*
> 185 E Stevens Way NE
> University of Washington
> Seattle, WA 98195-2350
>


-- 
*Laura Arjona *
Washington Research Foundation Innovation Postdoctoral Fellow in
Neuroengineering

*Paul G. Allen School of Computer Science & Engineering*
185 E Stevens Way NE
University of Washington
Seattle, WA 98195-2350

Re: Version compatibility problem

[Luke Stutters]

Dear Laura,

If you need to build and run GNU Radio 3.8 on a recent Linux kernel and not
just install it from packages, you may find the following notes useful:
https://docs.google.com/document/d/17gbDc_l32wbNIrXopUWIr1pOpu_Ty8tTeC4t12Ah_XE/edit?usp=sharing

This is just a simplified version of the guide on the Ettus wiki, but for
Ubuntu 19.10:
https://kb.ettus.com/Building_and_Installing_the_USRP_Open-Source_Toolchain_(UHD_and_GNU_Radio)_on_Linux

I was going to add it to the GNU Radio wiki but it does some things that
are unsuitable for a lot of systems, like installing self-compiled software
in /usr instead of /usr/local and patching numpy in-place to work round
Python 3.7 changes.

However, the simpler approach avoided Python and C++ environment-related
issues for me, and I just needed to test something quickly.

Best wishes,

On Wed, 12 Feb 2020 at 23:07, Laura Arjona  wrote:

> sorry, typed it wrong
> ~$ which gnradio-config-info
> /usr/local/bin/gnuradio-config-info
>
> On Wed, Feb 12, 2020 at 3:03 PM Laura Arjona  wrote:
>
>> Thank you Marcus.
>>
>> I think I am going to install ubuntu again, since I really  need to have
>> gnuradio working asap.
>>
>> It says nothing
>> ~$ which gnradio-config-info
>>
>> :~$ gnuradio-config-info --version
>> 3.8.0.0
>>
>> On Wed, Feb 12, 2020 at 2:42 PM Müller, Marcus (CEL) 
>> wrote:
>>
>>> huh. Seems to be more than one installation in the prefix?!
>>> what does `which gnuradio-config-info` say?
>>>
>>>
>>> On Wed, 2020-02-12 at 13:52 -0800, Laura Arjona wrote:
>>> > Thank you,
>>> >
>>> > I got rid of all the folders named  gnuradio, and it seems to be
>>> > uninstalled, because when  I run uninstall  I get Package 'gnuradio'
>>> > is not installed, so not removed
>>> >
>>> > But I still get
>>> > #  gnuradio-config-info --version
>>> > 3.8.0.0
>>> >
>>> >
>>> >
>>> > On Wed, Feb 12, 2020 at 12:47 PM Müller, Marcus (CEL) <
>>> > muel...@kit.edu> wrote:
>>> > > Hi Laura,
>>> > >
>>> > > first of all, unless you really want to work *on* GNU Radio,
>>> > > there's
>>> > > little reason to install it using PyBOMBS. At the very least, on
>>> > > Debian
>>> > > testing, there's native GNU Radio 3.8 packages, and for Fedora and
>>> > > Ubuntu, GNU Radio has binary packages that you can just install and
>>> > > use
>>> > > to develop your out-of-tree modules and GNU Radio applications.
>>> > >
>>> > > However, PyBOMBS will have installed GNU Radio 3.8 into the prefix
>>> > > ~/gnuradio. So, if you just move that out of the way, or delete it,
>>> > > then you should have no access to GNU Radio 3.8.0.0 anymore.
>>> > >
>>> > > Best regards,
>>> > > Marcus
>>> > >
>>> > > On Wed, 2020-02-12 at 12:12 -0800, Laura Arjona wrote:
>>> > > > Good morning,
>>> > > >
>>> > > > In short, I installed gnuradio 3.8 following the tutorial  in the
>>> > > github site
>>> > > > sudo -H pip3 install PyBOMBS
>>> > > > pybombs auto-config
>>> > > > pybombs recipes add-defaults
>>> > > > pybombs prefix init ~/gnuradio -R gnuradio-default
>>> > > >
>>> > > > but I got problems with the python path, then removed gnuradio,
>>> > > and re-installed the version 3.7.
>>> > > >
>>> > > > But when I check the version with gnuradio-config-info --version
>>> > > > I still get version 3.8.0.
>>> > > >
>>> > > > Because of the version I have other eros when building my oot-
>>> > > modules.
>>> > > >
>>> > > >
>>> > > > Any advice there?
>>> > > >
>>> > > > Thanks!
>>> > > >
>>> > > >
>>> >
>>> >
>>>
>>
>>
>> --
>> *Laura Arjona *
>> Washington Research Foundation Innovation Postdoctoral Fellow in
>> Neuroengineering
>>
>> *Paul G. Allen School of Computer Science & Engineering*
>> 185 E Stevens Way NE
>> University of Washington
>> Seattle, WA 98195-2350
>>
>
>
> --
> *Laura Arjona *
> Washington Research Foundation Innovation Postdoctoral Fellow in
> Neuroengineering
>
> *Paul G. Allen School of Computer Science & Engineering*
> 185 E Stevens Way NE
> University of Washington
> Seattle, WA 98195-2350
>