Pybomb gnuradio installation doesn't install gr-uhd

I just installed gnuradio and uhd via pybomb, sourced the env file in
the prefix dir, and attempted to do “from gnuradio import uhd”. gnuradio
imports and inspection shows it’s the prefixed version, but uhd fails
with ImportError: No module named uhd.

Do I need to pass pybomb some kind of special instruction to get gr-uhd
installed?

Thanks,
-Doug

On Thu, Jul 17, 2014 at 1:58 PM, Anderson, Douglas J. <
[email protected]> wrote:

[…]

Just not sure if this is a an issue with pybomb, the gnuradio recipe, or
my setup…

So, gnuradio only builds gr-uhd if it detects uhd? Maybe I’ll take a look
at where it’s looking, and where uhd actually exists.

-Doug

Yeah, that sounds like cmake isn’t finding the installed uhd library and
so
is not building gr-uhd.

You might use ‘./pybombs rnd gnuradio’ to blow away gnuradio completely
from pybombs to make sure there’s no left-over configuration steps that
are
preventing it from finding uhd.

Tom

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Usually, when GNU Radio is built and UHD is present, gr-uhd will be
built and installed automatically.
But to get this completely straight:
from gnuradio import uhd
fails, right? Because if there was no submodule uhd in gnuradio, I
think you should get a different Error:

from gnuradio import doesntexist
Traceback (most recent call last):
File “”, line 1, in
ImportError: cannot import name doesntexist

Greetings,
Marcus

On 17.07.2014 18:45, Anderson, Douglas J. wrote:

_______________________________________________ Discuss-gnuradio
mailing list [email protected]
Discuss-gnuradio Info Page

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTyAPuAAoJEBQ6EdjyzlHtLXQH+wWjPmYbNO++90J+blLPJmZP
s2fGllEZFNo+w9aPl6RixNFqmXqc+keR709fNWT5arI0LqlGAQVqK2Z5Jk74K+1x
YO5N6lVm0Qs9l8MZWPYZwDHDIf/FTKxBDXjNBKGRNBf43wlpFjdBmF+i9OmBu2hJ
xu5RgXR7qSpm5JciU9KuoeuleDUPoA3O4PKH4FOUX5poTlN6NZYRXu7OXl//DwA0
H9I+s5qyPBXxMCMUJ8kAJDU+WPZZyIBi3PQPWtMzVLkPBV1gpJbGER5btMPCiDij
hVoQQHhR8Ocy7XxHH0L+4ClYe4FtckYBQJYQl6TYoeGh9k4Zj3FzSgveTJ8FZyc=
=L1Kf
-----END PGP SIGNATURE-----

Marcus, I think everything is being done correctly. I did have uhd
installed (via pybomb) before gnuradio, and I’ve reinstalled both.


$ ./pybombs verify uhd
[…]
100% tests passed, 0 tests failed out of 16

Total Test time (real) = 1.02 sec
$ ./pybombs verify gnuradio
[…]
97% tests passed, 3 tests failed out of 86

Total Test time (real) = 54.09 sec

failed tests were fecapi stuff, unrelated to uhd I believe

$ source …/prefix/setup_env.sh
$ python -c “from gnuradio import uhd”
Traceback (most recent call last):
File “”, line 1, in
ImportError: cannot import name uhd


Just not sure if this is a an issue with pybomb, the gnuradio recipe, or
my setup…

So, gnuradio only builds gr-uhd if it detects uhd? Maybe I’ll take a
look at where it’s looking, and where uhd actually exists.

-Doug


From: discuss-gnuradio-bounces+danderson=removed_email_address@domain.invalid
[discuss-gnuradio-bounces+danderson=removed_email_address@domain.invalid] on behalf
of Marcus M. [[email protected]]
Sent: Thursday, July 17, 2014 11:12 AM
To: [email protected]
Subject: Re: [Discuss-gnuradio] pybomb gnuradio installation doesn’t
install gr-uhd

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Usually, when GNU Radio is built and UHD is present, gr-uhd will be
built and installed automatically.
But to get this completely straight:
from gnuradio import uhd
fails, right? Because if there was no submodule uhd in gnuradio, I
think you should get a different Error:

from gnuradio import doesntexist
Traceback (most recent call last):
File “”, line 1, in
ImportError: cannot import name doesntexist

Greetings,
Marcus

On 17.07.2014 18:45, Anderson, Douglas J. wrote:

_______________________________________________ Discuss-gnuradio
mailing list [email protected]
Discuss-gnuradio Info Page

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTyAPuAAoJEBQ6EdjyzlHtLXQH+wWjPmYbNO++90J+blLPJmZP
s2fGllEZFNo+w9aPl6RixNFqmXqc+keR709fNWT5arI0LqlGAQVqK2Z5Jk74K+1x
YO5N6lVm0Qs9l8MZWPYZwDHDIf/FTKxBDXjNBKGRNBf43wlpFjdBmF+i9OmBu2hJ
xu5RgXR7qSpm5JciU9KuoeuleDUPoA3O4PKH4FOUX5poTlN6NZYRXu7OXl//DwA0
H9I+s5qyPBXxMCMUJ8kAJDU+WPZZyIBi3PQPWtMzVLkPBV1gpJbGER5btMPCiDij
hVoQQHhR8Ocy7XxHH0L+4ClYe4FtckYBQJYQl6TYoeGh9k4Zj3FzSgveTJ8FZyc=
=L1Kf
-----END PGP SIGNATURE-----


Discuss-gnuradio mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Huh, strange… I’m trying to see a pattern in you disabled components,
but fail to find one. I think Tom was right, this was probably due to
CMake missing something on a previous run and now not catching up with
everything.
Hint: After doing your clean rebuild, you could have a look at the
CMakeCache search for your prefix in the various include paths; maybe
CMake (out of some misfortune or other) didn’t look into your prefix
directory.

Greetings,
Marcus

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ah ok, now your error matches what I was expecting, which we both can
pretend is a good thing :wink:

you could do several things to find where everything went wrong:

  1. check if
    prefix/lib(64)/python(2.7)/site-packages/gnuradio/uhd
    exists
  2. Check if UHD was really installed properly; if it was, there will
    be executables like uhd_usrp_probe in your prefix/bin directory, and
    headers in your prefix/include/uhd folder
  3. Check the build directory of GNU Radio, to make sure
    (CMakeCache.txt) to check if the GNU Radio build system noticed UHD.

Greetings,
Marcus

On 17.07.2014 19:58, Anderson, Douglas J. wrote:

stuff, unrelated to uhd I believe $ source …/prefix/setup_env.sh $
a look at where it’s looking, and where uhd actually exists.

Greetings, Marcus

gr-uhd installed?

_______________________________________________ Discuss-gnuradio
mailing list [email protected]
Discuss-gnuradio Info Page

_______________________________________________ Discuss-gnuradio
mailing list [email protected]
Discuss-gnuradio Info Page

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTyBT6AAoJEBQ6EdjyzlHt0ZEH/07i7/7794rHNyZIhKbmP9Pg
3y+FJXSOotA0aW1uZWpCykQD/7lGYRoLmKlHvYW8jzfhX6l8dEIJ2J2NXTFzzmZ0
wvSZdXmMU7Py49CocK5r88u1Z3PcVBTt5aB8QazC6unfxbwImSXQsh0ABuDFRj4Y
mQJySND6srWN1HOegnam6/1qgqZmurxmGR+UtS9/e7/mTxbTV9qP+7dyTiKljGjN
6AUdW+iR8Ms34UJz3r0CYstJ82GpHhMQE45cAx3JBz2PkWwFbdNkSKVVMvhVW9hV
NdfmIPON2exWmv13bI6RacWP0s7Y0sHgwe7P1urQsGRQRDejiIojKcCjHm0pYRk=
=3jRB
-----END PGP SIGNATURE-----

Thanks Tom and Marcus,

Yeah not sure about the error discrepancy, must have been paraphrasing
:slight_smile:

UHD is where it should be and was detected successfully by cmake, but
these couple lines from CMakeCache.txt make me realize I have bigger
problems than just gr-uhd:

_gr_disabled_components:INTERNAL=doxygen;sphinx;gr-fft;gr-filter;gr-analog;gr-digital;gr-atsc;gr-comedi;gr-channels;gr-pager;gr-qtgui;gr-trellis;gr-uhd;gr-video-sdl;gr-vocoder;gr-wavelet;gr-wxgui;gr-zeromq
_gr_enabled_components:INTERNAL=python-support;testing-support;volk;gnuradio-runtime;gr-ctrlport;gr-blocks;gnuradio-companion;gr-fec;gr-audio;gr-noaa;gr-utils;gr-fcd

I have no idea why half the included modules are disabled.

I’ll go ahead and do a pybomb rnd as Tom suggest and see what happens.

V/r,
-Doug

Wish I had a clever solution to all this, but I ended up just nuking my
prefix and pybombs dirs and starting over with pybombs -> uhd ->
gnuradio. All is good now. I think it was in fact a failed build early
on that wasn’t cleaning up quite right.

Thanks!

-Doug

On Thu, Jul 17, 2014 at 6:20 PM, Anderson, Douglas J. <
[email protected]> wrote:

Wish I had a clever solution to all this, but I ended up just nuking my
prefix and pybombs dirs and starting over with pybombs -> uhd -> gnuradio.
All is good now. I think it was in fact a failed build early on that wasn’t
cleaning up quite right.

Thanks!

-Doug

Yeah, there’s definitely a more elegant solution, but you’d have to know
the system really well. And likely the amount of time it would take to
get
there would be greater than just rebuilding everything :slight_smile:

Tom