Gnuradio-companion

GNU Radio
1

gnuradio-config-info -v

v3.6.4.1-106-gf1dbf510

On bot x86_64 and ARM gnuradio used to work now I get a pop-up
complaining about PYTHONPATH.
“export PYTHONPATH=/usr/lib/python2.7” on ARM and “export
PYTHONPATH=/usr/lib64/python2.7” on openSUSE doesn’t help.

I even rebuilt gnuradio on x86_64 in case something in an update caused
a problem.
73 … Sid.

2

Try a “sudo ldconfig”.

Ralph.

3

On 23/04/13 14:51, Bastian B. wrote:

for me that usually means I forgot
sudo ldconfig

Best,
Bastian

That’s not it.
When I initially installed it, gnuradio-companion worked on openSUSE
x86_64 and Ubuntu ARM for some days, so my guess was that something in
subsequent updates caused the problem.

That’s why I rebuilt the ARM version but got exactly the same problem.
73 … Sid.

–
Sid B. … Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks

4

On 23 Apr 2013 10:51, Sid B. wrote:

On 23/04/13 14:51,
Bastian B. wrote:

Hello Sid, On 04/23/2013 03:46 PM, Sid
Boyce wrote:

gnuradio-config-info -v v3.6.4.1-106-gf1dbf510

On bot x86_64 and ARM gnuradio used to work now I get a pop-up
complaining about PYTHONPATH. “export PYTHONPATH=/usr/lib/python2.7” on
ARM and “export PYTHONPATH=/usr/lib64/python2.7” on openSUSE doesn’t
help.

for me that usually means I forgot sudo ldconfig Best,
Bastian

That’s not it.
When I initially installed it,
gnuradio-companion worked on openSUSE
x86_64 and Ubuntu ARM for some
days, so my guess was that something in
subsequent updates caused the
problem.

That’s why I rebuilt the ARM version but got exactly the
same problem.
73 … Sid.

If you initially installed from binary, and
then installed from source, the PYTHONPATH locations are different.

A
typical source install installs to /usr/local whereas a packaged install
installs to /usr

5

On 23/04/13 14:46, Sid B. wrote:

73 … Sid.

Discuss-gnuradio mailing list
[email protected]
Discuss-gnuradio Info Page
I rebuilt gnuradio, still getting the same error with
gnuradio-companion.
“Cannot import gnuradio”.
Presumably this is a python module which I don’t have.

When I originally built gnuradio, gnuradio-companion worked on x86_64
and on ARM.
The next time I launched it I got the error on both platforms.
Pointers please.
73 … Sid.

6

caused a problem.
73 … Sid.

In fact, here’s a fun little script I wrote a while back to find the
appropriate pythonpath on your system.

7

On 06/05/13 00:39, Marcus D. Leech wrote:

caused a problem.
http://www.sbrac.org

Discuss-gnuradio mailing list
[email protected]
Discuss-gnuradio Info Page
Thanks again Marcus,
The problem with the build-gnuradio script is that it is set up to build
on Ubuntu and Fedora but no good for openSUSE.
73 … Sid.

8

Thanks again Marcus,
The problem with the build-gnuradio script is that it is set up to
build on Ubuntu and Fedora but no good for openSUSE.
73 … Sid.

When somebody sends me a reliable recipe for building on OpenSuse (and
detecting that it’s an OpenSuse system), I’ll be happy to update
build-gnuradio to support it.

9

I always build from source as there are some additions from dl2stg
needed for HiQSDR support.
I think I’ll ask him to submit them upstream.

cat /usr/src/gnuradio_audio.diff

diff --git a/gr-audio/lib/alsa/audio_alsa_source.cc
b/gr-audio/lib/alsa/audio_alsa_source.cc
index 4f0042b…fe41e43 100644
— a/gr-audio/lib/alsa/audio_alsa_source.cc
+++ b/gr-audio/lib/alsa/audio_alsa_source.cc
@@ -95,6 +95,7 @@ audio_alsa_source::audio_alsa_source (int
sampling_rate,
int error;
int dir;

  • hwParamsSet = false;
    // open the device for capture
    error = snd_pcm_open(&d_pcm_handle, d_device_name.c_str (),
    SND_PCM_STREAM_CAPTURE, 0);
    @@ -231,11 +232,15 @@ audio_alsa_source::check_topology (int ninputs,
    int noutputs)
    return false;
    }
  • // set the parameters into the driver…
  • err = snd_pcm_hw_params(d_pcm_handle, d_hw_params);
  • if (err < 0){
  • output_error_msg (“snd_pcm_hw_params failed”, err);
  • return false;

  • // SG

  • if (!hwParamsSet) {

  •  // set the parameters into the driver...

  •  err = snd_pcm_hw_params(d_pcm_handle, d_hw_params);

  •  if (err < 0){

  •     output_error_msg ("snd_pcm_hw_params failed", err);

  •     return false;

  •  }

  •  hwParamsSet = true;

    }

    d_buffer_size_bytes =
    diff --git a/gr-audio/lib/alsa/audio_alsa_source.h
    b/gr-audio/lib/alsa/audio_alsa_source.h
    index e38af38…7fdcdb5 100644
    — a/gr-audio/lib/alsa/audio_alsa_source.h
    +++ b/gr-audio/lib/alsa/audio_alsa_source.h
    @@ -101,6 +101,9 @@ protected:
    int work_s32_2x1 (int noutput_items,
    gr_vector_const_void_star &input_items,
    gr_vector_void_star &output_items);

+private:

  • bool hwParamsSet;
    };

#endif /* INCLUDED_AUDIO_ALSA_SOURCE_H */
73 … Sid.

10

On 06/05/13 00:34, Marcus D. Leech wrote:

caused a problem.
Presumably this is a python module which I don’t have.
Senior Staff Specialist, Cricket Coach
apt-get or the like), it will have installed under /usr
PYTHONPATH to.

–
Marcus L.
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org
Thanks Marcus,
I found the problem, python2.7 and python3.2 and python3.3 are installed
and it was picking python3.
“cmake -DPYTHON_EXECUTABLE=/usr/bin/python2.7
-DPYTHON_INCLUDE_DIR=/usr/include/python2.7
-DPYTHON_LIBRARY=/usr/lib64/libpython2.7.so -DCMAKE_INSTALL_PREFIX=/usr
…” fixed it.
73 … Sid.

11

On 06/05/13 02:09, Marcus D. Leech wrote:

–
Marcus L.
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org

Discuss-gnuradio mailing list
[email protected]
Discuss-gnuradio Info Page
I have the script so I’ll have a look.
73 … Sid.