On Wed, Apr 20, 2005 at 10:22:03AM -0700, Jonathan Jacky wrote:
>
> >ImportError: No module named _gnuradio_swig_python
>
> I fixed it.
>
> On Mac OS X, the build creates _gnuradio_swig_python.dylib. But
> python's import statement will only import files ending in .py, .pyc,
> and .so (I found
ImportError: No module named _gnuradio_swig_python
I fixed it.
On Mac OS X, the build creates _gnuradio_swig_python.dylib. But
python's import statement will only import files ending in .py, .pyc,
and .so (I found this by trying "python -vv").
I just put made a symbolic link _gnuradio_swig_python
On Fri, Apr 15, 2005 at 04:58:17PM -0700, Jonathan Jacky wrote:
>
> I build gnuradio-core from the 2.5 tarball on Mac OS X.
>
> After make and make install completed without error messages,
> I tried make check in my gnuradio-core-2.5. (I learned here in January
> that on OS X, make install must
I build gnuradio-core from the 2.5 tarball on Mac OS X.
After make and make install completed without error messages,
I tried make check in my gnuradio-core-2.5. (I learned here in January
that on OS X, make install must precede make check).
Every one of the qa_*.py checks fails with this same tr
