Re: [Discuss-gnuradio] GNURadio Windows Errors with OsmoSDR
t;fix" was applied.
>
> >>> import subprocess
> >>> print subprocess.check_call("where python27.dll")
> C:\Program Files\GNURadio-3.7\gr-python27\DLLs\python27.dll
> C:\Program Files\GNURadio-3.7\gr-python27\python27.dll
> C:\Python27\python27.dll
> C:\Program Files (x86)\Nmap\python27.dll
> 0
>
> >>> import sys
> >>> print(sys.executable)
> C:\Program Files\GNURadio-3.7\bin\..\gr-python27\python.exe
>
> >>> for p in sys.path:
> ... print p
>
> C:\Program Files\GNURadio-3.7\gr-python27\Lib\site-packages
> C:\Program Files\GNURadio-3.7\gr-python27\dlls
> C:\Program Files\GNURadio-3.7\gr-python27\libs
> C:\Program Files\GNURadio-3.7\gr-python27\lib
> C:\Program Files\GNURadio-3.7\lib\site-packages
> C:\Program Files\GNURadio-3.7\gr-python27\Lib\site-packages\pkgconfig
> C:\Program Files\GNURadio-3.7\gr-python27\Lib\site-packages\gtk-2.0\glib
> C:\Program Files\GNURadio-3.7\gr-python27\Lib\site-packages\gtk-2.0
> C:\Program Files\GNURadio-3.7\gr-python27\Lib\site-packages\wx-3.0-msw
> C:\Program Files\GNURadio-3.7\gr-python27\Lib\site-packages\sphinx
> C:\Program
> Files\GNURadio-3.7\gr-python27\Lib\site-packages\lxml-3.4.4-py2.7-win.amd64.egg
> C:\Program Files\GNURadio-3.7\gr-python27\python27.zip
> C:\Program Files\GNURadio-3.7\gr-python27\lib\plat-win
> C:\Program Files\GNURadio-3.7\gr-python27\lib\lib-tk
> C:\Program Files\GNURadio-3.7\gr-python27
> C:\Program Files\GNURadio-3.7\gr-python27\lib\site-packages\PIL
> C:\Program
> Files\GNURadio-3.7\gr-python27\lib\site-packages\pip-9.0.1-py2.7.egg
> C:\Program
> Files\GNURadio-3.7\gr-python27\lib\site-packages\wheel-0.29.0-py2.7.egg
> C:\Program
> Files\GNURadio-3.7\gr-python27\lib\site-packages\cython-0.28.5-py2.7-win-amd64.egg
> C:\Program
> Files\GNURadio-3.7\gr-python27\lib\site-packages\numpy-1.16.4-py2.7-win-amd64.egg
> C:\Program
> Files\GNURadio-3.7\gr-python27\lib\site-packages\cheetah-2.4.4-py2.7-win-amd64.egg
> C:\Program
> Files\GNURadio-3.7\gr-python27\lib\site-packages\setuptools-0.0.0-py2.7.egg
> C:\Program
> Files\GNURadio-3.7\gr-python27\lib\site-packages\lxml-3.6.0-py2.7-win-amd64.egg
> C:\Program
> Files\GNURadio-3.7\gr-python27\lib\site-packages\matplotlib-2.0.0-py2.7-win-amd64.egg
> C:\Program
> Files\GNURadio-3.7\gr-python27\lib\site-packages\cycler-0.10.0-py2.7.egg
> C:\Program
> Files\GNURadio-3.7\gr-python27\lib\site-packages\functools32-3.2.3.post2-py2.7.egg
> C:\Program
> Files\GNURadio-3.7\gr-python27\lib\site-packages\python_dateutil-2.8.0-py2.7.egg
> C:\Program
> Files\GNURadio-3.7\gr-python27\lib\site-packages\bitarray-0.8.1-py2.7-win-amd64.egg
> C:\Program
> Files\GNURadio-3.7\gr-python27\Lib\site-packages\setuptools-0.0.0-py2.7.egg
> C:\Program
> Files\GNURadio-3.7\gr-python27\Lib\site-packages\functools32-3.2.3.post2-py2.7.egg
> C:\Program
> Files\GNURadio-3.7\gr-python27\Lib\site-packages\lxml-3.4.4-py2.7-win.amd64.egg
>
> >>> import numpy
> >>> import gnuradio
> >>> import osmosdr
> Traceback (most recent call last):
> File "", line 1, in
> File "C:\Program
> Files\GNURadio-3.7\lib\site-packages\osmosdr\__init__.py", line 26, in
>
> from osmosdr_swig import *
> File "C:\Program
> Files\GNURadio-3.7\lib\site-packages\osmosdr\osmosdr_swig.py", line 17, in
>
> _osmosdr_swig = swig_import_helper()
> File "C:\Program
> Files\GNURadio-3.7\lib\site-packages\osmosdr\osmosdr_swig.py", line 16, in
> swig_import_helper
> return importlib.import_module('_osmosdr_swig')
> File "C:\Program
> Files\GNURadio-3.7\gr-python27\lib\importlib\__init__.py", line 37, in
> import_module
> __import__(name)
> ImportError: No module named _osmosdr_swig
>
> So evidently even though the dll is gone from System32 the issue still
> persists.
>
> Thoughts? Again I appreciate your help.
>
> Patrick
>
> -Original Message-
> From: Geof Nieboer
> Sent: Tuesday, June 25, 2019 9:06 AM
> To: W3AXL Patrick
> Cc: discuss-gnuradio@gnu.org
> Subject: Re: [Discuss-gnuradio] GNURadio Windows Errors with OsmoSDR
>
> OK, I think a clue here is that a python dll is installed in System32.
> Windows will always check System32 regardless of the PATH, so something
> there might be causing some misdirection.
>
> Try this... run the "run_gr.bat" file and once in, run python by simply
> entering "python"
>
> Then enter;
> import subprocess
> print subprocess.check_call("where python27.dll") import sys
> print(sys.executable)
> for p in sys.path:
> import numpy
> import gnuradio
> import osmosdr
>
> This will get us some basic path info and we can see where it breaks.
> THEN repeat, but before running the python command enter "cd
> ..\gr-python27" and see if the results are different.
> Finally, repeat the above but using the run_gr_d.bat instead. That runs
> the debug version of python, and it's less likely you have a debug version
> installed on your machine, so if _d works that's just further confirmation.
>
> My suspicion is that the above will show that that the DLL from
> System32 is being loaded in the first case, but not in the others. If so,
> then the solution is to remove python27.dll from System32 (which belongs to
> a different python installation) and move it to wherever you have a 64-bit
> install of python27 (since it at least appears to be a 64 bit Dll) in the
> same folder as python.exe. If you have more than, then copy it to each one
> that doesn't have one of it's own.
>
> If none of this worked, please send screen shots back.
>
> I don't believe many Python distros are still installing to System32 for
> exactly this reason.
>
> >
>
>
>
>
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] GNURadio Windows Errors with OsmoSDR
e-packages\pip-9.0.1-py2.7.egg
C:\Program
Files\GNURadio-3.7\gr-python27\lib\site-packages\wheel-0.29.0-py2.7.egg
C:\Program
Files\GNURadio-3.7\gr-python27\lib\site-packages\cython-0.28.5-py2.7-win-amd64.egg
C:\Program
Files\GNURadio-3.7\gr-python27\lib\site-packages\numpy-1.16.4-py2.7-win-amd64.egg
C:\Program
Files\GNURadio-3.7\gr-python27\lib\site-packages\cheetah-2.4.4-py2.7-win-amd64.egg
C:\Program
Files\GNURadio-3.7\gr-python27\lib\site-packages\setuptools-0.0.0-py2.7.egg
C:\Program
Files\GNURadio-3.7\gr-python27\lib\site-packages\lxml-3.6.0-py2.7-win-amd64.egg
C:\Program
Files\GNURadio-3.7\gr-python27\lib\site-packages\matplotlib-2.0.0-py2.7-win-amd64.egg
C:\Program
Files\GNURadio-3.7\gr-python27\lib\site-packages\cycler-0.10.0-py2.7.egg
C:\Program
Files\GNURadio-3.7\gr-python27\lib\site-packages\functools32-3.2.3.post2-py2.7.egg
C:\Program
Files\GNURadio-3.7\gr-python27\lib\site-packages\python_dateutil-2.8.0-py2.7.egg
C:\Program
Files\GNURadio-3.7\gr-python27\lib\site-packages\bitarray-0.8.1-py2.7-win-amd64.egg
C:\Program
Files\GNURadio-3.7\gr-python27\Lib\site-packages\setuptools-0.0.0-py2.7.egg
C:\Program
Files\GNURadio-3.7\gr-python27\Lib\site-packages\functools32-3.2.3.post2-py2.7.egg
C:\Program
Files\GNURadio-3.7\gr-python27\Lib\site-packages\lxml-3.4.4-py2.7-win.amd64.egg
>>> import numpy
>>> import gnuradio
>>> import osmosdr
Traceback (most recent call last):
File "", line 1, in
File "C:\Program Files\GNURadio-3.7\lib\site-packages\osmosdr\__init__.py",
line 26, in
from osmosdr_swig import *
File "C:\Program
Files\GNURadio-3.7\lib\site-packages\osmosdr\osmosdr_swig.py", line 17, in
_osmosdr_swig = swig_import_helper()
File "C:\Program
Files\GNURadio-3.7\lib\site-packages\osmosdr\osmosdr_swig.py", line 16, in
swig_import_helper
return importlib.import_module('_osmosdr_swig')
File "C:\Program Files\GNURadio-3.7\gr-python27\lib\importlib\__init__.py",
line 37, in import_module
__import__(name)
ImportError: No module named _osmosdr_swig
So evidently even though the dll is gone from System32 the issue still persists.
Thoughts? Again I appreciate your help.
Patrick
-Original Message-
From: Geof Nieboer
Sent: Tuesday, June 25, 2019 9:06 AM
To: W3AXL Patrick
Cc: discuss-gnuradio@gnu.org
Subject: Re: [Discuss-gnuradio] GNURadio Windows Errors with OsmoSDR
OK, I think a clue here is that a python dll is installed in System32.
Windows will always check System32 regardless of the PATH, so something there
might be causing some misdirection.
Try this... run the "run_gr.bat" file and once in, run python by simply
entering "python"
Then enter;
import subprocess
print subprocess.check_call("where python27.dll") import sys
print(sys.executable)
for p in sys.path:
import numpy
import gnuradio
import osmosdr
This will get us some basic path info and we can see where it breaks.
THEN repeat, but before running the python command enter "cd ..\gr-python27"
and see if the results are different.
Finally, repeat the above but using the run_gr_d.bat instead. That runs the
debug version of python, and it's less likely you have a debug version
installed on your machine, so if _d works that's just further confirmation.
My suspicion is that the above will show that that the DLL from
System32 is being loaded in the first case, but not in the others. If so, then
the solution is to remove python27.dll from System32 (which belongs to a
different python installation) and move it to wherever you have a 64-bit
install of python27 (since it at least appears to be a 64 bit Dll) in the same
folder as python.exe. If you have more than, then copy it to each one that
doesn't have one of it's own.
If none of this worked, please send screen shots back.
I don't believe many Python distros are still installing to System32 for
exactly this reason.
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] GNURadio Windows Errors with OsmoSDR
OK, I think a clue here is that a python dll is installed in System32.
Windows will always check System32 regardless of the PATH, so
something there might be causing some misdirection.
Try this... run the "run_gr.bat" file and once in, run python by
simply entering "python"
Then enter;
import subprocess
print subprocess.check_call("where python27.dll")
import sys
print(sys.executable)
for p in sys.path:
import numpy
import gnuradio
import osmosdr
This will get us some basic path info and we can see where it breaks.
THEN repeat, but before running the python command enter "cd
..\gr-python27" and see if the results are different.
Finally, repeat the above but using the run_gr_d.bat instead. That
runs the debug version of python, and it's less likely you have a
debug version installed on your machine, so if _d works that's just
further confirmation.
My suspicion is that the above will show that that the DLL from
System32 is being loaded in the first case, but not in the others. If
so, then the solution is to remove python27.dll from System32 (which
belongs to a different python installation) and move it to wherever
you have a 64-bit install of python27 (since it at least appears to be
a 64 bit Dll) in the same folder as python.exe. If you have more
than, then copy it to each one that doesn't have one of it's own.
If none of this worked, please send screen shots back.
I don't believe many Python distros are still installing to System32
for exactly this reason.
On 6/25/19, W3AXL Patrick wrote:
> Geof
>
>
>
> Yes, I’m running from that batch file. I agree, it’s a very bizzare error.
> I’ve only been able to find a couple mentions to my issue online and they’re
> all on other platforms like OSX or Linux.
>
>
>
> Attached is the dependency check on _osmosdr_swig.pyd – the older dependency
> checker tool didn’t want to work in Win10 but this one did. I don’t see any
> erorrs apart from the incorrect checksums it’s reporting in the bottom
> pane.
>
>
>
> Thanks again for your willingness to help. I really want to get GRC up and
> working properly on this machine and I know how strange this error is.
>
>
>
> Patrick
>
>
>
> From: Geof Nieboer
> Sent: Tuesday, June 25, 2019 6:33 AM
> To: W3AXL Patrick
> Cc: Kyeong Su Shin ; discuss-gnuradio@gnu.org
> Subject: Re: [Discuss-gnuradio] GNURadio Windows Errors with OsmoSDR
>
>
>
> Patrick,
>
>
>
> Just to confirm, you started GRC by running the run_GRC.bat file or the link
> on the start menu? Assuming so. If not that’s the problem and ignore the
> rest.
>
>
>
> There is little program out there called “dependency checker” that is
> invaluable for these issues. Download it and find the .pyd module file
> below with the import error. Open it in that program. It will display the
> chain of DLLs it is looking for and if something is missing it should
> appear. (You will get false errors about system libraries and may need to
> add directories to the search tree path).
>
>
>
> So if you run that and there is a missing DLL that seems GR related then let
> us know which it is , this would indicate a problem in the installer.
>
>
>
> Next option is the DLL is somewhere in the system and somehow the GRC isn’t
> finding it, which would be odd but possible.
>
>
>
> It’s a very odd error in general, running an RTL based flow graph is tested
> when I package the installers.
>
>
>
>
>
> On Mon, Jun 24, 2019 at 23:09 W3AXL Patrick <mailto:patr...@w3axl.com> > wrote:
>
> Hi Kyeong
>
>
>
> This is running a GRC file inside of GNURadio Companion. Something is indeed
> broken.
>
>
>
> I simply ran the Win64 installer for GNURadio from the Windows builds site
> linked by the GNURadio wiki. I recall last year I had this same issue on my
> Windows system and gave up using GRC on Windows because of it. It’s a pain
> to load up my linux box every time I want to use GNURadio though.
>
>
>
> Thanks for the input
>
>
>
> Patrick
>
>
>
> From: Kyeong Su Shin mailto:kss...@postech.ac.kr> >
> Sent: Monday, June 24, 2019 9:52 PM
> To: W3AXL Patrick mailto:patr...@w3axl.com> >;
> discuss-gnuradio@gnu.org <mailto:discuss-gnuradio@gnu.org>
> Subject: RE: [Discuss-gnuradio] GNURadio Windows Errors with OsmoSDR
>
>
>
> Hello Patrick:
>
>
>
> Are you running a GNU Radio Python code? Or, are you running a GRC file
> using GNU Radio Companion?
>
>
>
> If you are running a Python code generated from GNU Radio Companion, you
> should be running that code using "GNU Radio Command Prompt" (which comes
> with correct library PATH variables).
>
>
>
> If you are
Re: [Discuss-gnuradio] GNURadio Windows Errors with OsmoSDR
Patrick,
Just to confirm, you started GRC by running the run_GRC.bat file or the
link on the start menu? Assuming so. If not that’s the problem and ignore
the rest.
There is little program out there called “dependency checker” that is
invaluable for these issues. Download it and find the .pyd module file
below with the import error. Open it in that program. It will display the
chain of DLLs it is looking for and if something is missing it should
appear. (You will get false errors about system libraries and may need to
add directories to the search tree path).
So if you run that and there is a missing DLL that seems GR related then
let us know which it is , this would indicate a problem in the installer.
Next option is the DLL is somewhere in the system and somehow the GRC isn’t
finding it, which would be odd but possible.
It’s a very odd error in general, running an RTL based flow graph is tested
when I package the installers.
On Mon, Jun 24, 2019 at 23:09 W3AXL Patrick wrote:
> Hi Kyeong
>
>
>
> This is running a GRC file inside of GNURadio Companion. Something is
> indeed broken.
>
>
>
> I simply ran the Win64 installer for GNURadio from the Windows builds site
> linked by the GNURadio wiki. I recall last year I had this same issue on my
> Windows system and gave up using GRC on Windows because of it. It’s a pain
> to load up my linux box every time I want to use GNURadio though.
>
>
>
> Thanks for the input
>
>
>
> Patrick
>
>
>
> *From:* Kyeong Su Shin
> *Sent:* Monday, June 24, 2019 9:52 PM
> *To:* W3AXL Patrick ; discuss-gnuradio@gnu.org
> *Subject:* RE: [Discuss-gnuradio] GNURadio Windows Errors with OsmoSDR
>
>
>
> Hello Patrick:
>
>
>
> Are you running a GNU Radio Python code? Or, are you running a GRC file
> using GNU Radio Companion?
>
>
>
> If you are running a Python code generated from GNU Radio Companion, you
> should be running that code using "GNU Radio Command Prompt" (which comes
> with correct library PATH variables).
>
>
>
> If you are running a GRC file using GNU Radio Companion, then I guess
> something is broken..
>
>
>
> Also, please note that the GNU Radio Windows distribution comes with its
> own Python interpreter (which you can use by using GNU Radio Command
> Prompt", and does not touch or use the Python interpreter on your system.
>
>
>
> Regards,
>
> Kyeong Su Shin
>
>
> --
>
> *보낸* *사람**:* W3AXL Patrick 대신 Discuss-gnuradio <
> discuss-gnuradio-bounces+ksshin=postech.ac...@gnu.org>
> *보낸* *날짜**:* 2019년 6월 25일 화요일 오전 10:50:11
> *받는* *사람**:* discuss-gnuradio@gnu.org
> *제목**:* [Discuss-gnuradio] GNURadio Windows Errors with OsmoSDR
>
>
>
> Hi all on the list,
>
>
>
> I’ve been tearing my hair out trying to solve an issue I’m having with a
> clean install of GNURadio using the Windows builds.
>
>
>
> When trying to run a simple flowgraph, with an RTL-SDR source connected to
> a frequency sink, I receive the following traceback:
>
>
>
> Traceback (most recent call last):
>
> File "C:\Users\Patrick\Documents\top_block.py", line 29, in
>
> import osmosdr
>
> File "C:\Program
> Files\GNURadio-3.7\lib\site-packages\osmosdr\__init__.py", line 26, in
>
>
> from osmosdr_swig import *
>
> File "C:\Program
> Files\GNURadio-3.7\lib\site-packages\osmosdr\osmosdr_swig.py", line 17, in
>
>
> _osmosdr_swig = swig_import_helper()
>
> File "C:\Program
> Files\GNURadio-3.7\lib\site-packages\osmosdr\osmosdr_swig.py", line 16, in
> swig_import_helper
>
> return importlib.import_module('_osmosdr_swig')
>
> File "C:\Program
> Files\GNURadio-3.7\gr-python27\lib\importlib\__init__.py", line 37, in
> import_module
>
> __import__(name)
>
> ImportError: No module named _osmosdr_swig
>
>
>
> I think this is a problem with my PATH, or with the installation of
> GNURadio, but I can’t figure out how to fix it. There is almost no info on
> anyone else having errors like this with GRC so I’m stumped.
>
>
>
> Additionally, on this clean install of GNURadio, I receive over a hundred
> of errors similar to this one during startup of GRC:
>
>
>
> Warning: Block with key "xxx" already exists.
>
> Ignoring: C:\Program
> Files\GNURadio-3.7\share\gnuradio\grc\blocks\xxx.xml
>
>
>
> I feel as if these two issues might be related in some way.
>
>
>
> I would appreciate any help. My system is running Win10 and I have the
> latest Python 2.7 installed.
>
>
>
> Thanks to all,
>
>
>
> Patrick
> ___
> 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] GNURadio Windows Errors with OsmoSDR
Hi Kyeong
This is running a GRC file inside of GNURadio Companion. Something is
indeed broken.
I simply ran the Win64 installer for GNURadio from the Windows builds site
linked by the GNURadio wiki. I recall last year I had this same issue on my
Windows system and gave up using GRC on Windows because of it. It’s a pain
to load up my linux box every time I want to use GNURadio though.
Thanks for the input
Patrick
From: Kyeong Su Shin
Sent: Monday, June 24, 2019 9:52 PM
To: W3AXL Patrick ; discuss-gnuradio@gnu.org
Subject: RE: [Discuss-gnuradio] GNURadio Windows Errors with OsmoSDR
Hello Patrick:
Are you running a GNU Radio Python code? Or, are you running a GRC file
using GNU Radio Companion?
If you are running a Python code generated from GNU Radio Companion, you
should be running that code using "GNU Radio Command Prompt" (which comes
with correct library PATH variables).
If you are running a GRC file using GNU Radio Companion, then I guess
something is broken..
Also, please note that the GNU Radio Windows distribution comes with its
own Python interpreter (which you can use by using GNU Radio Command
Prompt", and does not touch or use the Python interpreter on your system.
Regards,
Kyeong Su Shin
_
보낸 사람: W3AXL Patrick mailto:patr...@w3axl.com> >
대신 Discuss-gnuradio mailto:discuss-gnuradio-
bounces+ksshin=postech.ac...@gnu.org> >
보낸 날짜: 2019년 6월 25일 화요일 오전 10:50:11
받는 사람: discuss-gnuradio@gnu.org <mailto:discuss-gnuradio@gnu.org>
제목: [Discuss-gnuradio] GNURadio Windows Errors with OsmoSDR
Hi all on the list,
I’ve been tearing my hair out trying to solve an issue I’m having with a
clean install of GNURadio using the Windows builds.
When trying to run a simple flowgraph, with an RTL-SDR source connected to
a frequency sink, I receive the following traceback:
Traceback (most recent call last):
File "C:\Users\Patrick\Documents\top_block.py", line 29, in
import osmosdr
File "C:\Program Files\GNURadio-3.7\lib\site-
packages\osmosdr\__init__.py", line 26, in
from osmosdr_swig import *
File "C:\Program Files\GNURadio-3.7\lib\site-
packages\osmosdr\osmosdr_swig.py", line 17, in
_osmosdr_swig = swig_import_helper()
File "C:\Program Files\GNURadio-3.7\lib\site-
packages\osmosdr\osmosdr_swig.py", line 16, in swig_import_helper
return importlib.import_module('_osmosdr_swig')
File "C:\Program Files\GNURadio-3.7\gr-
python27\lib\importlib\__init__.py", line 37, in import_module
__import__(name)
ImportError: No module named _osmosdr_swig
I think this is a problem with my PATH, or with the installation of
GNURadio, but I can’t figure out how to fix it. There is almost no info on
anyone else having errors like this with GRC so I’m stumped.
Additionally, on this clean install of GNURadio, I receive over a hundred
of errors similar to this one during startup of GRC:
Warning: Block with key "xxx" already exists.
Ignoring: C:\Program Files\GNURadio-
3.7\share\gnuradio\grc\blocks\xxx.xml
I feel as if these two issues might be related in some way.
I would appreciate any help. My system is running Win10 and I have the
latest Python 2.7 installed.
Thanks to all,
Patrick
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] GNURadio Windows Errors with OsmoSDR
Hello Patrick:
Are you running a GNU Radio Python code? Or, are you running a GRC file using
GNU Radio Companion?
If you are running a Python code generated from GNU Radio Companion, you should
be running that code using "GNU Radio Command Prompt" (which comes with correct
library PATH variables).
If you are running a GRC file using GNU Radio Companion, then I guess something
is broken..
Also, please note that the GNU Radio Windows distribution comes with its own
Python interpreter (which you can use by using GNU Radio Command Prompt", and
does not touch or use the Python interpreter on your system.
Regards,
Kyeong Su Shin
보낸 사람: W3AXL Patrick 대신 Discuss-gnuradio
보낸 날짜: 2019년 6월 25일 화요일 오전 10:50:11
받는 사람: discuss-gnuradio@gnu.org
제목: [Discuss-gnuradio] GNURadio Windows Errors with OsmoSDR
Hi all on the list,
I’ve been tearing my hair out trying to solve an issue I’m having with a clean
install of GNURadio using the Windows builds.
When trying to run a simple flowgraph, with an RTL-SDR source connected to a
frequency sink, I receive the following traceback:
Traceback (most recent call last):
File "C:\Users\Patrick\Documents\top_block.py", line 29, in
import osmosdr
File "C:\Program Files\GNURadio-3.7\lib\site-packages\osmosdr\__init__.py",
line 26, in
from osmosdr_swig import *
File "C:\Program
Files\GNURadio-3.7\lib\site-packages\osmosdr\osmosdr_swig.py", line 17, in
_osmosdr_swig = swig_import_helper()
File "C:\Program
Files\GNURadio-3.7\lib\site-packages\osmosdr\osmosdr_swig.py", line 16, in
swig_import_helper
return importlib.import_module('_osmosdr_swig')
File "C:\Program Files\GNURadio-3.7\gr-python27\lib\importlib\__init__.py",
line 37, in import_module
__import__(name)
ImportError: No module named _osmosdr_swig
I think this is a problem with my PATH, or with the installation of GNURadio,
but I can’t figure out how to fix it. There is almost no info on anyone else
having errors like this with GRC so I’m stumped.
Additionally, on this clean install of GNURadio, I receive over a hundred of
errors similar to this one during startup of GRC:
Warning: Block with key "xxx" already exists.
Ignoring: C:\Program
Files\GNURadio-3.7\share\gnuradio\grc\blocks\xxx.xml
I feel as if these two issues might be related in some way.
I would appreciate any help. My system is running Win10 and I have the latest
Python 2.7 installed.
Thanks to all,
Patrick
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] GNURadio Windows Errors with OsmoSDR
Hi all on the list,
I've been tearing my hair out trying to solve an issue I'm having with a
clean install of GNURadio using the Windows builds.
When trying to run a simple flowgraph, with an RTL-SDR source connected to a
frequency sink, I receive the following traceback:
Traceback (most recent call last):
File "C:\Users\Patrick\Documents\top_block.py", line 29, in
import osmosdr
File "C:\Program
Files\GNURadio-3.7\lib\site-packages\osmosdr\__init__.py", line 26, in
from osmosdr_swig import *
File "C:\Program
Files\GNURadio-3.7\lib\site-packages\osmosdr\osmosdr_swig.py", line 17, in
_osmosdr_swig = swig_import_helper()
File "C:\Program
Files\GNURadio-3.7\lib\site-packages\osmosdr\osmosdr_swig.py", line 16, in
swig_import_helper
return importlib.import_module('_osmosdr_swig')
File "C:\Program
Files\GNURadio-3.7\gr-python27\lib\importlib\__init__.py", line 37, in
import_module
__import__(name)
ImportError: No module named _osmosdr_swig
I think this is a problem with my PATH, or with the installation of
GNURadio, but I can't figure out how to fix it. There is almost no info on
anyone else having errors like this with GRC so I'm stumped.
Additionally, on this clean install of GNURadio, I receive over a hundred of
errors similar to this one during startup of GRC:
Warning: Block with key "xxx" already exists.
Ignoring: C:\Program
Files\GNURadio-3.7\share\gnuradio\grc\blocks\xxx.xml
I feel as if these two issues might be related in some way.
I would appreciate any help. My system is running Win10 and I have the
latest Python 2.7 installed.
Thanks to all,
Patrick
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
