discuss-gnuradio
[Top][All Lists]
Advanced

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

Re: [Discuss-gnuradio] GNU Radio release 3.6.3 available for download


From: Josh Blum
Subject: Re: [Discuss-gnuradio] GNU Radio release 3.6.3 available for download
Date: Wed, 16 Jan 2013 22:05:02 -0600
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2


On 01/16/2013 09:37 PM, Marcus D. Leech wrote:
> On 16/01/13 09:02 PM, Michael L Kornegay wrote:
>> Mike,
>>
>>>> maybe even the scan thing I noted above.  See problem loading the dylib 
>>>> below:  
>>>>
>>>> ImportError: 
>>>> dlopen(/opt/local/lib/python2.7/site-packages/osmosdr/_osmosdr_swig.so, 
>>>> 2): Library not loaded: libgnuradio-osmosdr.0.dylib
>>>> Referenced from: 
>>>> /opt/local/lib/python2.7/site-packages/osmosdr/_osmosdr_swig.so
>>>> Reason: image not found
>>>>
>>>> Seems like I am missing one final detail that glues the proper loading of 
>>>> the dynamic libraries?  
>>> I'm wondering where "libgnuradio-osmosdr.0.dylib" is located.  Usually this 
>>> would be installed into ${prefix}/lib (so, /opt/local/lib in your case).
>> Yes it was in /opt/local/lib.  Don't know why the system can't find it.  
>>
>> If I cd to /opt/local/lib and then run gnu radio-companion, works great, if 
>> I am not cd to that directory it fails every time.  
>>
>>
>> I also tried adding /opt/local/lib to the PATH but that did not help.  \
> PATH is used for locating executable programs, not libraries.
> 
> UNIX-like systems often use LD_LIBRARY_PATH to extend the
> system-configured paths for libraries.
> 

if you come from a windows background, PATH is used for dlls and
executables. However, for OSX, you will want to set DYLD_LIBRARY_PATH to
contain your dylibs

-josh

> 
>> At least I can run successfully now, even though have to cd to that 
>> directory.
>>
>> I think Alex might have also said something similar not that I say this, I 
>> think he said he had to copy libs to the directory of his executable.  
>>
>> If you think of any potential solution, let me know.  Otherwise I guess I 
>> will play with things for a while with this work around, and revisit trying 
>> to figure out why later.  
>>
>> Thanks for your suggestions and help,
>> mlk
>>
>>
>> _______________________________________________
>> Discuss-gnuradio mailing list
>> address@hidden
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>
>>
> 
> 



reply via email to

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