GNU bug report logs - #40952
gnuradio-osmosdr: no hook into gnuradio block directory?

Previous Next

Full log

View this message in rfc822 format

From: Christopher Howard <christopher <at> librehacker.com>
To: Guillaume Le Vaillant <glv <at> posteo.net>
Cc: 40952 <at> debbugs.gnu.org
Subject: bug#40952: gnuradio-osmosdr: no hook into gnuradio block directory?
Date: Thu, 30 Apr 2020 06:07:34 -0800

[Message part 1 (text/plain, inline)]

Works now, thanks! Am able to feed data in from HackRF using osmosdr
source block.

(As a side note to posterity reading this: I have the hackrf system
service set in my config.scm, as described in the hackrf package
description.)

-- 
Christopher Howard
p: +1 (907) 374-0257
w: https://librehacker.com
social: https://gnusocial.club/librehacker
gpg: ADDEAADE5D607C8D (keys.gnupg.net)

On Thu, 2020-04-30 at 11:03 +0200, Guillaume Le Vaillant wrote:
> Christopher Howard <christopher <at> librehacker.com> skribis:
> 
> > I can see the osmosdr sink, insert it into the flow graph, and
> > change
> > the settings. However, when trying to build the flow graph, I
> > receive
> > the following error. Apparently you need to also update whatever
> > environment variable controls the python module load path.
> > 
> > <<< Welcome to GNU Radio Companion 3.8.0.0 >>>
> > 
> > Block paths:
> > 	/home/christopher/.guix-profile/share/gnuradio/grc/blocks
> > 	/gnu/store/h2igg2gcbx6ds8wbvlkqz0dkplvwjxbd-gnuradio-
> > 3.8.0.0/share/gnuradio/grc/blocks
> > 
> > Generating: '/home/christopher/Scratch/test.py'
> > 
> > Executing: /gnu/store/c0ysvb6s92kwwnmkgdhnspllxvd3f231-python-
> > 3.7.4/bin/python3 -u /home/christopher/Scratch/test.py
> > 
> > Warning: failed to XInitThreads()
> > Traceback (most recent call last):
> >   File "/home/christopher/Scratch/test.py", line 33, in <module>
> >     import osmosdr
> > ModuleNotFoundError: No module named 'osmosdr'
> > 
> > > > > Done (return code 1)
> 
> I pushed a patch to set PYTHONPATH in the profile when gnuradio is
> intalled (commit f03e5ca59f2f099693def2c8e6ff409e5b4ed40a). I guess
> I had another installed package that had set it, because I didn't get
> this error.
> Could you try if it works for you?

[Screenshot from 2020-04-30 06-04-23.png (image/png, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.