Its working!  this is fantastic.  Brian, you were right.  the command to 
install hackrf must come before installing osmosdr

Thanks everyone!

Jay.

On Jan 10, 2015, at 4:52 PM, Brian Dickman <brian.dick...@gmail.com> wrote:

> In general I think the directions are good, but there's no way the order is 
> right. You'll want to run the hackrf install before installing gr-osmosdr. 
> Use "brew uninstall" against both hackrf and gr-osmosdr, then run them again 
> with hackrf first and gr-osmosdr second, so that the osmosdr configure/make 
> detects libhackrf and uses it. You should be off and running after that. 
> 
> --
> Brian
> 
> On Sat, Jan 10, 2015 at 4:29 PM, Jay Hamlin <redwoodra...@mac.com> wrote:
> Brian-  Thank you!
> 
> Since I am on Macintosh, my step 1 command is:
>    otool -l /usr/local/Cellar/gqrx/HEAD/Gqrx.app/Contents/MacOs/Gqrx | grep 
> osmo
> 
> And I get the exact same path as you with offset 24 except I have version 
> 0.1.5.
> 
> Step 2 fails - ok, so osmodr did not get created with libhackrf compiled in!  
> This is a start.
> 
> I am following the directions here: 
> https://github.com/andresv/homebrew-gnuradio
> 
> The step for building osmodr I think is this one:
>   brew install gr-osmosdr gr-baz —HEAD
> 
> Is that right?
> 
> Thanks,
> Jay.
> 
> On Jan 10, 2015, at 2:24 PM, Brian Dickman <brian.dick...@gmail.com> wrote:
> 
>> A good first step is to make sure that your osmosdr is linked with 
>> libhackrf. Perhaps there is an easier way to do this? Here's my approach.
>> 
>> At a terminal prompt:
>> 
>> 1) otool -l `which gqrx` | grep osmo
>> 
>> (those are backticks up by the escape key, not single quotes)
>> 
>> You should get back the full path to your libosmosdr dylib. Take that 
>> filename and feed it into the next command (for example, mine says "name 
>> /usr/local/lib/libgnuradio-osmosdr.0.1.2git.dylib (offset 24)" so I'll use 
>> that path, but use the result you get):
>> 
>> 2) otool -l /usr/local/lib/libgnuradio-osmosdr.0.1.2git.dylib | grep hackrf
>> 
>> You should get a result back (for example, mine says "name 
>> /usr/local/lib/libhackrf.0.dylib (offset 24)"). If you don't, then osmosdr 
>> did not get created with libhackrf compiled in. You can also run without the 
>> grep to see all the info that otool knows about libhackrf.
>> 
>> --
>> Brian
>> 
>> On Sat, Jan 10, 2015 at 10:16 AM, Jay Hamlin <redwoodra...@mac.com> wrote:
>> I have tried hard to solve this problem on my own but I’m stuck and need 
>> help.  I installed all the software on Macintosh using Homebrew following 
>> the instructions carefully.  I used hackrf_spiflash and hackrf_cpldjtag to 
>> update the firmware and hackrf_info reports good information like everything 
>> is fine. But hackRF does not show up as a device in Gqrx and osmocom_fft 
>> reports no device found.  I saw one other report like this in the archives 
>> but with no resolution.  It seems like there must be a simple configuration 
>> or path wrong but I can’t figure it out.  Please help.  Thanks.  Jay.
>> _______________________________________________
>> HackRF-dev mailing list
>> HackRF-dev@greatscottgadgets.com
>> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>> 
> 
> 

_______________________________________________
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Reply via email to