From: Guillaume Le Vaillant <glv@posteo.net>
To: Christopher Howard <christopher@librehacker.com>
Cc: 40952@debbugs.gnu.org
Subject: bug#40952: gnuradio-osmosdr: no hook into gnuradio block directory?
Date: Thu, 30 Apr 2020 11:03:42 +0200 [thread overview]
Message-ID: <87a72twdjl.fsf@yamatai> (raw)
In-Reply-To: <d6dd53b0ce9231c26e789a2fc8347f2d3292f2ee.camel@librehacker.com>
[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]
Christopher Howard <christopher@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?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2020-04-30 9:06 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
2020-04-30 9:03 ` Guillaume Le Vaillant [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a72twdjl.fsf@yamatai \
--to=glv@posteo.net \
--cc=40952@debbugs.gnu.org \
--cc=christopher@librehacker.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).