gnuradio-osmosdr: no hook into gnuradio block directory?

  • Done
  • quality assurance status badge
Details
3 participants
  • Christopher Howard
  • Christopher Howard
  • Guillaume Le Vaillant
Owner
unassigned
Submitted by
Christopher Howard
Severity
normal

Debbugs page

Christopher Howard wrote 5 years ago
(address . bug-guix@gnu.org)
2daa37de70a83d3ffad747710e95e429eeeea6aa.camel@qlfiles.net
Hi, I installed gnuradio and gnuradio-osmosdr, but when I open
gnuradio, none of the osmosdr blocks are available from gnuradio blocks
list. Specifically, I was looking for osmosdr source block, which I am
familiar with from using gnuradio under Debian. I believe the problem
is that the osmosdr blocks are not in the directory where gnuradio-
companion is looking for blocks.

When starting up gnuradio-companion, stdout indicates grc is looking for blocks here:

/gnu/store/h2igg2gcbx6ds8wbvlkqz0dkplvwjxbd-gnuradio-3.8.0.0/share/gnuradio/grc/blocks

But osmosdr blocks are in

/gnu/store/ppb504vizb32f4w2s5f0yd6i4xpy41nz-gnuradio-osmosdr-0.2.0/share/gnuradio/grc/blocks/

Evidentally gnuradio package needs to be enhanced to create a per-
profile merged directory from all gnuradio- block packages that are
installed. Unless there is some way to extend the gnuradio search path
through environment variables.

--
Christopher Howard
p: +1 (907) 374-0257
gpg: ADDEAADE5D607C8D (keys.gnupg.net)
Guillaume Le Vaillant wrote 5 years ago
(address . christopher@librehacker.com)(address . 40952@debbugs.gnu.org)
874kt2heju.fsf@yamatai
Christopher Howard <christopher.howard@qlfiles.net> skribis:

Toggle quote (20 lines)
> Hi, I installed gnuradio and gnuradio-osmosdr, but when I open
> gnuradio, none of the osmosdr blocks are available from gnuradio blocks
> list. Specifically, I was looking for osmosdr source block, which I am
> familiar with from using gnuradio under Debian. I believe the problem
> is that the osmosdr blocks are not in the directory where gnuradio-
> companion is looking for blocks.
>
> When starting up gnuradio-companion, stdout indicates grc is looking for blocks here:
>
> /gnu/store/h2igg2gcbx6ds8wbvlkqz0dkplvwjxbd-gnuradio-3.8.0.0/share/gnuradio/grc/blocks
>
> But osmosdr blocks are in
>
> /gnu/store/ppb504vizb32f4w2s5f0yd6i4xpy41nz-gnuradio-osmosdr-0.2.0/share/gnuradio/grc/blocks/
>
> Evidentally gnuradio package needs to be enhanced to create a per-
> profile merged directory from all gnuradio- block packages that are
> installed. Unless there is some way to extend the gnuradio search path
> through environment variables.

Hi Christopher,

I pushed a fix (commit cf480830e22e7725b8607b5b895e49f74d4e1525) that
should put the paths to installed third-party blocks in GRC_BLOCKS_PATH,
and allow gnuradio-companion to see them. Could you check if it works
for you?
-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQQkUwKxurH4Z/3KlryPP4Yfgut6mgUCXqk9FQAKCRCPP4Yfgut6
mqbsAP9HNywEjjTSek8Nq09IyPNHaKNt3KOhzyA9L9vu0yqZnQEAud6zUPPm5K6E
VwP7f8jasdhbFFeIyipnLdWt76gxsgs=
=IOK1
-----END PGP SIGNATURE-----

Christopher Howard wrote 5 years ago
(name . Guillaume Le Vaillant)(address . glv@posteo.net)(address . 40952@debbugs.gnu.org)
f9c92e216f9fa9d4516da32041e5e9482571ca4f.camel@librehacker.com
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.

--
Christopher Howard
p: +1 (907) 374-0257
gpg: ADDEAADE5D607C8D (keys.gnupg.net)

On Wed, 2020-04-29 at 10:38 +0200, Guillaume Le Vaillant wrote:
Toggle quote (36 lines)
> Christopher Howard <christopher.howard@qlfiles.net> skribis:
>
> > Hi, I installed gnuradio and gnuradio-osmosdr, but when I open
> > gnuradio, none of the osmosdr blocks are available from gnuradio
> > blocks
> > list. Specifically, I was looking for osmosdr source block, which I
> > am
> > familiar with from using gnuradio under Debian. I believe the
> > problem
> > is that the osmosdr blocks are not in the directory where gnuradio-
> > companion is looking for blocks.
> >
> > When starting up gnuradio-companion, stdout indicates grc is
> > looking for blocks here:
> >
> > /gnu/store/h2igg2gcbx6ds8wbvlkqz0dkplvwjxbd-gnuradio-
> > 3.8.0.0/share/gnuradio/grc/blocks
> >
> > But osmosdr blocks are in
> >
> > /gnu/store/ppb504vizb32f4w2s5f0yd6i4xpy41nz-gnuradio-osmosdr-
> > 0.2.0/share/gnuradio/grc/blocks/
> >
> > Evidentally gnuradio package needs to be enhanced to create a per-
> > profile merged directory from all gnuradio- block packages that are
> > installed. Unless there is some way to extend the gnuradio search
> > path
> > through environment variables.
>
> Hi Christopher,
>
> I pushed a fix (commit cf480830e22e7725b8607b5b895e49f74d4e1525) that
> should put the paths to installed third-party blocks in
> GRC_BLOCKS_PATH,
> and allow gnuradio-companion to see them. Could you check if it works
> for you?
Christopher Howard wrote 5 years ago
(name . Guillaume Le Vaillant)(address . glv@posteo.net)(address . 40952@debbugs.gnu.org)
d6dd53b0ce9231c26e789a2fc8347f2d3292f2ee.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'

Toggle quote (2 lines)
>>> Done (return code 1)

--
Christopher Howard
p: +1 (907) 374-0257
gpg: ADDEAADE5D607C8D (keys.gnupg.net)

On Wed, 2020-04-29 at 06:56 -0800, Christopher Howard wrote:
Toggle quote (6 lines)
> 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.
>
Guillaume Le Vaillant wrote 5 years ago
(name . Christopher Howard)(address . christopher@librehacker.com)(address . 40952@debbugs.gnu.org)
87a72twdjl.fsf@yamatai
Christopher Howard <christopher@librehacker.com> skribis:

Toggle quote (25 lines)
> 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?
-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQQkUwKxurH4Z/3KlryPP4Yfgut6mgUCXqqUbgAKCRCPP4Yfgut6
mtKAAP4+tXkybBK4R9s+EoeSpglMQecYY9m5G4Cj2S0rYvTsyQD/cXnkjZv3oB+c
BH/WUY8Z2nctXYzAszA/a3vAmyXsuAQ=
=JtaW
-----END PGP SIGNATURE-----

Christopher Howard wrote 5 years ago
(name . Guillaume Le Vaillant)(address . glv@posteo.net)(address . 40952@debbugs.gnu.org)
88c813aec10c74c29f1267a7056ff270dae1dd91.camel@librehacker.com
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
gpg: ADDEAADE5D607C8D (keys.gnupg.net)

On Thu, 2020-04-30 at 11:03 +0200, Guillaume Le Vaillant wrote:
Toggle quote (34 lines)
> 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?
Guillaume Le Vaillant wrote 5 years ago
(address . 40952-done@debbugs.gnu.org)(name . Christopher Howard)(address . christopher@librehacker.com)
877dxxvz2y.fsf@yamatai
Christopher Howard <christopher@librehacker.com> skribis:

Toggle quote (7 lines)
> 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.)

Ok, closing the bug.
-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQQkUwKxurH4Z/3KlryPP4Yfgut6mgUCXqrdpQAKCRCPP4Yfgut6
ml1sAP9WH2kDPWqGugB0EC0kIsY0pjoUusiM3nO2nAMZuT1AtgD+M8Ukv0sWbnPQ
+IfGuqQ0aLFj6IHrIRf5aTlHlea9BQ4=
=7BZb
-----END PGP SIGNATURE-----

Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 40952@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 40952
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch
You may also tag this issue. See list of standard tags. For example, to set the confirmed and easy tags
mumi command -t +confirmed -t +easy
Or, remove the moreinfo tag and set the help tag
mumi command -t -moreinfo -t +help