subject:"Re\: \[Discuss\-gnuradio\] No module named _runtime

Re: [Discuss-gnuradio] No module named _runtime_swig in version 3.7.11

2018-04-06 Thread Vladimir Komendantskiy

I fixed the error by deleting /etc/ld.so.cache:

$ sudo rm /etc/ld.so.cache
$ sudo ldconfig

I'm quoting the output of the commands you sent me. The output is the same
before and after deleting the cache. So they don't point at the source of
the issue.

$ gnuradio-config-info --enabled-components
python-support;testing-support;volk;doxygen;sphinx;
gnuradio-runtime;gr-ctrlport;gr-blocks;gnuradio-companion;
gr-fec;gr-fft;gr-filter;gr-analog;gr-digital;gr-dtv;gr-atsc;gr-audio;*
alsa;* oss;gr-comedi;gr-channels;gr-noaa;gr-pager;gr-qtgui;gr-
trellis;gr-uhd;gr-utils;gr-video-sdl;gr-vocoder;gr-fcd;
gr-wavelet;gr-wxgui;gr-zeromq

$ apt list --installed | grep gnuradio

WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.

$ ls -ld /usr/bin/python
lrwxrwxrwx 1 root root 9 Dec 13 22:39 /usr/bin/python -> python2.7

vk@alonzo:~/src/poanetwork/hbbft$ sudo ldconfig -v | grep gnuradio
ldconfig: Can't stat /usr/lib/digilent/adept: No such file or directory
ldconfig: Can't stat /usr/local/lib/i386-linux-gnu: No such file or
directory
ldconfig: Can't stat /usr/local/lib/i686-linux-gnu: No such file or
directory
ldconfig: Can't stat /lib/i686-linux-gnu: No such file or directory
ldconfig: Can't stat /usr/lib/i686-linux-gnu: No such file or directory
ldconfig: Can't stat /usr/local/lib/x86_64-linux-gnu: No such file or
directory
ldconfig: Path `/lib/x86_64-linux-gnu' given more than once
ldconfig: Path `/usr/lib/x86_64-linux-gnu' given more than once
ldconfig: /lib/i386-linux-gnu/ld-2.27.so is the dynamic linker, ignoring

libgnuradio-iio.so.0 -> libgnuradio-iio.so.0.2
libgnuradio-vocoder-3.7.11.1.so.0.0.0 -> libgnuradio-vocoder.so
libgnuradio-channels-3.7.11.1.so.0.0.0 -> libgnuradio-channels.so
libgnuradio-fcd-3.7.11.1.so.0.0.0 -> libgnuradio-fcd.so
libgnuradio-uhd-3.7.11.1.so.0.0.0 -> libgnuradio-uhd.so
libgnuradio-blocks-3.7.11.1.so.0.0.0 -> libgnuradio-blocks.so
libgnuradio-digital-3.7.11.1.so.0.0.0 -> libgnuradio-digital.so
libgnuradio-trellis-3.7.11.1.so.0.0.0 -> libgnuradio-trellis.so
libgnuradio-audio-3.7.11.1.so.0.0.0 -> libgnuradio-audio.so
libgnuradio-wavelet-3.7.11.1.so.0.0.0 -> libgnuradio-wavelet.so
libgnuradio-atsc-3.7.11.1.so.0.0.0 -> libgnuradio-atsc.so
libgnuradio-pager-3.7.11.1.so.0.0.0 -> libgnuradio-pager.so
libgnuradio-fec-3.7.11.1.so.0.0.0 -> libgnuradio-fec.so
libgnuradio-runtime-3.7.11.1.so.0.0.0 -> libgnuradio-runtime.so
libgnuradio-zeromq-3.7.11.1.so.0.0.0 -> libgnuradio-zeromq.so
libgnuradio-analog-3.7.11.1.so.0.0.0 -> libgnuradio-analog.so
libgnuradio-qtgui-3.7.11.1.so.0.0.0 -> libgnuradio-qtgui.so
libgnuradio-comedi-3.7.11.1.so.0.0.0 -> libgnuradio-comedi.so
libgnuradio-pmt-3.7.11.1.so.0.0.0 -> libgnuradio-pmt.so
libgnuradio-fft-3.7.11.1.so.0.0.0 -> libgnuradio-fft.so
libgnuradio-filter-3.7.11.1.so.0.0.0 -> libgnuradio-filter.so
libgnuradio-noaa-3.7.11.1.so.0.0.0 -> libgnuradio-noaa.so
libgnuradio-dtv-3.7.11.1.so.0.0.0 -> libgnuradio-dtv.so
libgnuradio-video-sdl-3.7.11.1.so.0.0.0 -> libgnuradio-video-sdl.so
libgnuradio-wxgui-3.7.11.1.so.0.0.0 -> libgnuradio-wxgui.so
ldconfig: /lib/x86_64-linux-gnu/ld-2.27.so is the dynamic linker, ignoring

ldconfig: /lib32/ld-2.27.so is the dynamic linker, ignoring

--Vladimir

On 6 April 2018 at 20:41, Cinaed Simson  wrote:

> On 04/06/2018 01:27 AM, Vladimir Komendantskiy wrote:
> >
> >
> > On 6 April 2018 at 00:22, Cinaed Simson  > > wrote:
> >
> > Type
> >
> >   gnuradio-config-info --prefix
> >
> > and post it.
> >
> > Whether or not you need to add anything to your PYTHONPATH or
> > LD_LIBRARY_PATH depends on where you installed it.
> >
> >
> > $ gnuradio-config-info --prefix
> > /usr/local
> >
> > Cheers,
> > Vladimir
>
> Post
>
>   gnuradio-config-info --enabled-components
>
> Make sure you're using python2 and not python3 when you start a shell
>
>   ls -ld /usr/bin/python
>
> Also, check
>
>   apt list --installed | grep gnuradio
>
> and
>
>   ldconfig -v | grep gnuradio
>
> -- Cinaed
>
>
>
>
>
>
>
>
>
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] No module named _runtime_swig in version 3.7.11

2018-04-05 Thread Cinaed Simson

Type

  gnuradio-config-info --prefix

and post it.

Whether or not you need to add anything to your PYTHONPATH or
LD_LIBRARY_PATH depends on where you installed it.

-- Cinaed

On 04/05/2018 02:52 AM, Vladimir Komendantskiy wrote:
> Thanks for your questions. I will be happy to clarify the issue. It
> should be clear though that I don't have two different installations of
> gnuradio on any single machine at any point in time.
> 
> This is what I'm doing. My goals are to install and run gnuradio. My
> distribution, as I wrote earlier, is Debian testing, codenamed Buster.
> My previous installation I had since last Summer was compiled from
> source and was working without any Python environment errors.
> Unfortunately I removed that installation in order to install the latest
> gnuradio. And that one didn't work.
> 
> Ways I tried, each one after removing any other gnuradio installations:
> 
> 1. Install from package: sudo apt install gnuradio. Installation
> successful. gnuradio-companion displays the error dialog and exits.
> 
> 
> 2. build-gnuradio. Compilation of gnuradio fails because of this issue:
> 
>  
> https://github.com/gnuradio/gnuradio/commit/00c6f258259c61f25dc220402a9d07544942b414
> 
> 
> I fixed the issue by applying the above patch. Compilation succeeds. The
> error dialog is the same and gnuradio-companion still doesn't work.
> 
> 
> 3. Compile gnuradio from github. Managed to compile but same error dialog.
> 
> Furthermore, in each of the 3 cases above I first tried running
> gnuradio-companion with the default environment: LD_LIBRARY_PATH
> and PYTHONPATH _empty_. When that didn't work, I set the environment
> according to the README and to my Python version:
> 
> $ export PYTHONPATH=/usr/local/lib/python2.7/dist-packages
> $ export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$HOME/local/lib
> 
> which didn't change the outcome a bit.
> 
> 
> For the sake of completeness, the dialog text is the following:
> 
> ==
> Cannot import gnuradio.
> 
> Is the model path environment variable set correctly?
>     All OS: PYTHONPATH
> 
> Is the library path environment variable set correctly?
>     Linux: LD_LIBRARY_PATH
>     Windows: PATH
>     MacOSX: DYLD_LIBRARY_PATH
> 
> 
> (No module named _runtime_swig)
> ==
> 
> 
> Any ideas apart from changing the Linux distribution? The distro has to
> stay. I can always go back to the version of gnuradio that worked but I
> have a feeling that the issue here is very minor and can be fixed if you
> know the details.
> 
> --Vladimir
> 
> 
> On 5 April 2018 at 00:02, Cinaed Simson  > wrote:
> 
> On 04/04/2018 08:58 AM, Vladimir Komendantskiy wrote:
> > Hi,
> >
> > I tried the latest Debian testing package of gnuradio and compiled from
> > git master (applying one version 3.7.12 patch to fix a compile-time 
> error).
> >
> > In both cases gnuradio-companion only displays the following error 
> dialog:
> 
> It's not clear what it is you're doing.
> 
> Bottom line, you can't have 2 installations of gnuradio on the same
> machine - if that's what you're doing.
> 
> Stick to one machine with only 1 installation of gnuradio - ideally a
> normal Debian install.
> 
> >
> > ==
> > Cannot import gnuradio.
> >
> > Is the model path environment variable set correctly?
> >     All OS: PYTHONPATH
> >
> > Is the library path environment variable set correctly?
> >     Linux: LD_LIBRARY_PATH
> >     Windows: PATH
> >     MacOSX: DYLD_LIBRARY_PATH
> >
> >
> > (No module named _runtime_swig)
> 
> Show us the answers to the above questions for PYTHONPATH,
> LD_LIBRARY_PATH.
> 
> Most likely they're not set correctly.
> 
> And why can't you use the default version 3.7.10 for Debian Jessie?
> Which version of Debian are you using?
> 
> -- Cinaed
> 
> > ==
> >
> > Is there a solution for that? I also tried setting the above mentioned
> > paths according to the git README to no avail.
> >
> > To be sure I tried on two different machines. One of those has a very
> > recent installation of Debian and no custom environment, only the
> > environment set by the distro.
> >
> > --Vladimir
> >
> >
> > ___
> > Discuss-gnuradio mailing list
> > Discuss-gnuradio@gnu.org 
> > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> 
> >
> 
> 
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org 
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> 
> 
> 
> 
> 
>

Re: [Discuss-gnuradio] No module named _runtime_swig in version 3.7.11

2018-04-05 Thread Vladimir Komendantskiy

Thanks for your questions. I will be happy to clarify the issue. It should
be clear though that I don't have two different installations of gnuradio
on any single machine at any point in time.

This is what I'm doing. My goals are to install and run gnuradio. My
distribution, as I wrote earlier, is Debian testing, codenamed Buster. My
previous installation I had since last Summer was compiled from source and
was working without any Python environment errors. Unfortunately I removed
that installation in order to install the latest gnuradio. And that one
didn't work.

Ways I tried, each one after removing any other gnuradio installations:

1. Install from package: sudo apt install gnuradio. Installation
successful. gnuradio-companion displays the error dialog and exits.

2. build-gnuradio. Compilation of gnuradio fails because of this issue:

  https://github.com/gnuradio/gnuradio/commit/00c6f258259c61f25dc220402a9d07
544942b414

I fixed the issue by applying the above patch. Compilation succeeds. The
error dialog is the same and gnuradio-companion still doesn't work.

3. Compile gnuradio from github. Managed to compile but same error dialog.

Furthermore, in each of the 3 cases above I first tried running
gnuradio-companion with the default environment: LD_LIBRARY_PATH
and PYTHONPATH _empty_. When that didn't work, I set the environment
according to the README and to my Python version:

$ export PYTHONPATH=/usr/local/lib/python2.7/dist-packages
$ export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$HOME/local/lib

which didn't change the outcome a bit.

For the sake of completeness, the dialog text is the following:

==
Cannot import gnuradio.

Is the model path environment variable set correctly?
All OS: PYTHONPATH

Is the library path environment variable set correctly?
Linux: LD_LIBRARY_PATH
Windows: PATH
MacOSX: DYLD_LIBRARY_PATH

(No module named _runtime_swig)
==

Any ideas apart from changing the Linux distribution? The distro has to
stay. I can always go back to the version of gnuradio that worked but I
have a feeling that the issue here is very minor and can be fixed if you
know the details.

--Vladimir

On 5 April 2018 at 00:02, Cinaed Simson  wrote:

> On 04/04/2018 08:58 AM, Vladimir Komendantskiy wrote:
> > Hi,
> >
> > I tried the latest Debian testing package of gnuradio and compiled from
> > git master (applying one version 3.7.12 patch to fix a compile-time
> error).
> >
> > In both cases gnuradio-companion only displays the following error
> dialog:
>
> It's not clear what it is you're doing.
>
> Bottom line, you can't have 2 installations of gnuradio on the same
> machine - if that's what you're doing.
>
> Stick to one machine with only 1 installation of gnuradio - ideally a
> normal Debian install.
>
> >
> > ==
> > Cannot import gnuradio.
> >
> > Is the model path environment variable set correctly?
> > All OS: PYTHONPATH
> >
> > Is the library path environment variable set correctly?
> > Linux: LD_LIBRARY_PATH
> > Windows: PATH
> > MacOSX: DYLD_LIBRARY_PATH
> >
> >
> > (No module named _runtime_swig)
>
> Show us the answers to the above questions for PYTHONPATH, LD_LIBRARY_PATH.
>
> Most likely they're not set correctly.
>
> And why can't you use the default version 3.7.10 for Debian Jessie?
> Which version of Debian are you using?
>
> -- Cinaed
>
> > ==
> >
> > Is there a solution for that? I also tried setting the above mentioned
> > paths according to the git README to no avail.
> >
> > To be sure I tried on two different machines. One of those has a very
> > recent installation of Debian and no custom environment, only the
> > environment set by the distro.
> >
> > --Vladimir
> >
> >
> > ___
> > Discuss-gnuradio mailing list
> > Discuss-gnuradio@gnu.org
> > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> >
>
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] No module named _runtime_swig in version 3.7.11

2018-04-04 Thread Cinaed Simson

On 04/04/2018 08:58 AM, Vladimir Komendantskiy wrote:
> Hi,
> 
> I tried the latest Debian testing package of gnuradio and compiled from
> git master (applying one version 3.7.12 patch to fix a compile-time error).
> 
> In both cases gnuradio-companion only displays the following error dialog:

It's not clear what it is you're doing.

Bottom line, you can't have 2 installations of gnuradio on the same
machine - if that's what you're doing.

Stick to one machine with only 1 installation of gnuradio - ideally a
normal Debian install.

> 
> ==
> Cannot import gnuradio.
> 
> Is the model path environment variable set correctly?
>     All OS: PYTHONPATH
> 
> Is the library path environment variable set correctly?
>     Linux: LD_LIBRARY_PATH
>     Windows: PATH
>     MacOSX: DYLD_LIBRARY_PATH
> 
> 
> (No module named _runtime_swig)

Show us the answers to the above questions for PYTHONPATH, LD_LIBRARY_PATH.

Most likely they're not set correctly.

And why can't you use the default version 3.7.10 for Debian Jessie?
Which version of Debian are you using?

-- Cinaed

> ==
> 
> Is there a solution for that? I also tried setting the above mentioned
> paths according to the git README to no avail.
> 
> To be sure I tried on two different machines. One of those has a very
> recent installation of Debian and no custom environment, only the
> environment set by the distro.
> 
> --Vladimir
> 
> 
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> 


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] No module named _runtime_swig in version 3.7.11

Re: [Discuss-gnuradio] No module named _runtime_swig in version 3.7.11

Re: [Discuss-gnuradio] No module named _runtime_swig in version 3.7.11

Re: [Discuss-gnuradio] No module named _runtime_swig in version 3.7.11

4 matches

Site Navigation

Mail list logo

Footer information