discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] 2 issues


From: Eric Blossom
Subject: Re: [Discuss-gnuradio] 2 issues
Date: Tue, 4 Sep 2007 11:07:40 -0700
User-agent: Mutt/1.5.9i

On Tue, Sep 04, 2007 at 01:54:55PM -0400, Michael Dickens wrote:
> 1) the file "wfm_rcv_file.py" has disappeared from gnuradio-examples/ 
> python/usrp.  Not sure if this was intended, but here's a patch to  
> "Makefile.am" to correct the compile.
> 
> Index: Makefile.am
> ===================================================================
> --- Makefile.am (revision 6291)
> +++ Makefile.am (working copy)
> @@ -37,8 +37,7 @@
>         usrp_wfm_rcv_pll.py                     \
>         usrp_wfm_rcv_sca.py                     \
>         usrp_wfm_rcv2_nogui.py                  \
> -       usrp_wxapt_rcv.py                       \
> -       wfm_rcv_file.py
> +       usrp_wxapt_rcv.py
> ourdatadir = $(exampledir)/usrp
> ourdata_DATA = $(EXTRA_DIST)

It was dropped because it doesn't follow the current coding
conventions.  Feel free to fix or reimplement.


> 2) On OSX, "make check" fails in gr-usrp, if the USRP module isn't  
> already installed .. it's trying to load the usrp's shared library,  
> but it's not yet installed.  I thought all of those were corrected  
> way back when, but it looks like one was missed.
> 
> Making check in gr-usrp
> Making check in src
> make  check-am
> make  check-TESTS
> Traceback (most recent call last):
>   File "./qa_usrp.py", line 24, in ?
>     import usrp1
>   File "/opt/gnuradio/gr-usrp/src/usrp1.py", line 6, in ?
>     import _usrp1
> ImportError: Failure linking new module: /GNURadio/gr-usrp/src/.libs/ 
> _usrp1.so: Library not loaded: /usr/local/lib/libusrp.0.dylib
>   Referenced from: /GNURadio/gr-usrp/src/.libs/_usrp1.so
>   Reason: image not found

Thanks for the report.  Seems like something is off here.
It's trying to make check against the installed library, which is
incorrect.

Can you please attempt to figure out what changed and when?  I don't
think there is anything that was deliberately changed that should have
caused this problem.

Eric




reply via email to

[Prev in Thread] Current Thread [Next in Thread]