Ctest can't find gnuradio module!

GNU Radio
1

Hi there,

Could someone help me fix this issue, when I try to run my tests, the
ctest
returns the following:
…
from gnuradio import gr, gr_unittest
ImportError: No module named gnuradio
…
Nonetheless, when I import any module from gnuradio in python terminal,
it
passes without any problem, and I can also run gnuradio-companion !
which I
found very strange.

Thank you in advance.
Mohamed

–
View this message in context:
http://gnuradio.4.n7.nabble.com/ctest-can-t-find-gnuradio-module-tp49344.html
Sent from the GnuRadio mailing list archive at Nabble.com.

2

On Tue, Jul 15, 2014 at 8:51 AM, mohamedx [email protected]
wrote:

found very strange.

Thank you in advance.
Mohamed

What version of GNU Radio? And how did you install it in the first
place?
When you ran cmake, did you see that “testing-support” was enabled? And,
just to make sure, you are running ctest within the build directory,
right?

Tom

3

Hi Tom,

Thank you for your prompt response.
I use 3.7.3 version, I’ve installed it from the source.
Here is what “cmake -Wno-dev …/” returns:

– Build type not specified: defaulting to release.
– Boost version: 1.54.0
– Found the following Boost libraries:
– filesystem
– system
Checking for GNU Radio Module: RUNTIME
– checking for module ‘gnuradio-runtime’
– package ‘gnuradio-runtime’ not found

  • INCLUDES=/usr/local/include
  • LIBS=/lib64/libgnuradio-runtime.so
    GNURADIO_RUNTIME_FOUND = TRUE
    – Configuring done
    – Generating done
    – Build files have been written to: /xxxxxxxxxxxx/build

So there is no “testing support”, and yes, I’m running ctest within
build
directory.
This a little bit strange, cmake didn’t find the runtime for the first
place !

I appreciate anything would help.

On Tue, Jul 15, 2014 at 3:21 PM, Tom R.-2 [via GnuRadio] <
[email protected]> wrote:

ImportError: No module named gnuradio
What version of GNU Radio? And how did you install it in the first place?

http://gnuradio.4.n7.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html!nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers!nabble%3Aemail.naml-instant_emails!nabble%3Aemail.naml-send_instant_email!nabble%3Aemail.naml

–

Graduate Student at Supélec, MSc, Advanced Wireless Communication
Systems,
Élève ingénieur à l’INPT en mobilité internationale.

4

On Tue, Jul 15, 2014 at 9:50 AM, mohamedx [email protected]
wrote:

– system
So there is no “testing support”, and yes, I’m running ctest within build
directory.
This a little bit strange, cmake didn’t find the runtime for the first
place !

I appreciate anything would help.

This doesn’t make sense. This looks like you’re trying to build your own
OOT module, not GNU Radio itself. So are you trying to run ctest on your
own code or actually run GNU Radio’s test suite?

And what’s happening with the "package ‘gnuradio-runtime’ not found’ is
that pkg-config is not finding the .pc file, which means it’s not in a
path
known to it (see PKG_CONFIG_PATH). However, cmake continued to look
explicitly for the headers and libraries and found them, which is why
GNURADIO_RUNTIME_FOUND = TRUE.

It’s very odd that you have the headers in /usr/local and the library in
/lib64, though. I’m thinking that this might have something to do with
your
ctest issue.

Tom