From: Christopher Howard <christopher@librehacker.com>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: 40952@debbugs.gnu.org
Subject: bug#40952: gnuradio-osmosdr: no hook into gnuradio block directory?
Date: Wed, 29 Apr 2020 17:11:11 -0800 [thread overview]
Message-ID: <d6dd53b0ce9231c26e789a2fc8347f2d3292f2ee.camel@librehacker.com> (raw)
In-Reply-To: <f9c92e216f9fa9d4516da32041e5e9482571ca4f.camel@librehacker.com>
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)
--
Christopher Howard
p: +1 (907) 374-0257
w: https://librehacker.com
social: https://gnusocial.club/librehacker
gpg: ADDEAADE5D607C8D (keys.gnupg.net)
On Wed, 2020-04-29 at 06:56 -0800, Christopher Howard wrote:
> The osmosdr sink and source blocks are showing up now after updating
> to
> the specified commit. I have to leave for work now, but was planning
> to
> try using the source block this evening with my HackRF SDR.
>
next prev parent reply other threads:[~2020-04-30 1:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 4:20 bug#40952: gnuradio-osmosdr: no hook into gnuradio block directory? Christopher Howard
2020-04-29 8:38 ` Guillaume Le Vaillant
2020-04-29 14:56 ` Christopher Howard
2020-04-30 1:11 ` Christopher Howard [this message]
2020-04-30 9:03 ` Guillaume Le Vaillant
2020-04-30 14:07 ` Christopher Howard
2020-04-30 14:16 ` Guillaume Le Vaillant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d6dd53b0ce9231c26e789a2fc8347f2d3292f2ee.camel@librehacker.com \
--to=christopher@librehacker.com \
--cc=40952@debbugs.gnu.org \
--cc=glv@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.