[Hackrf-dev] what is the story with gr-osmosdr not building?

Chuck McManis chuck.mcmanis at gmail.com
Tue Aug 1 15:43:58 EDT 2017


Okay, that was funny.
--Chuck

On Mon, Jul 31, 2017 at 11:49 PM, Anon Lister <listeranon at gmail.com> wrote:
> Builds fine for me. I suggest you try posting on discuss-gnuradio (if that
> is your end goal, see below,) however I suggest you first read [1] and [2].
> Specifically, list your goal(you mention gr-osmosdr, then the LimeSDR, on
> the hackrf mailing list, with no mention of your end goal), what you have
> tried sofar(did you build any other pieces of code first? What was the
> result of that?), and any error messages you encountered. This will help
> people better understand what your trying to do and explain the meaning of
> any error messages you are getting.
>
> The LimeSDR is a fairly new device, and the best place to ask questions
> about it seems to be the discourse page from myriadrf, found at [3] or you
> can visit their wiki found at [4] (However, once again, read [1] first.) It
> sounds like your new to Linux, if you just want to listen to radio, perhaps
> look at SDRConsole for a native windows program, which has a lower learning
> curve, and is closed source.)
>
> [1] http://www.catb.org/esr/faqs/smart-questions.html
> [2] http://xyproblem.info
> [3] https://discourse.myriadrf.org/c/projects/limesdr
> [4] https://wiki.myriadrf.org/Lime_Suite
>
> Cheers,
> -Anon
>
> On Aug 1, 2017 1:50 AM, "Chuck McManis" <chuck.mcmanis at gmail.com> wrote:
>
> Hi Dominic,
>
>> We're not in a position to support LimeSDR on this mailing list,
>
> I know, I much prefer my HackRF :-). Up to now I've "gotten away" with
> just using the packages rather than go into the FOSS dungeon to smelt
> metal to cast parts for a lathe so that I can create the tools that I
> need to get something done. Consider it an expression of my
> frustration. So begins my entry into the third level of hell, perhaps
> I'll blog about it :-). It does surprise me that HEAD on a 'major'
> package like gr-osmosdr would not even be buildable, (because that is
> typically the first test prior to merge a commit, does it still build)
> but as I've been digging into it, some of the inter-relationships
> between gnuradio, what Ettus started with (aka the uhd API) and the
> current state of affairs (about a half dozen SDRs bodged into the
> framework in one way or another) that the situation is far from
> "simple."
>
> Since the HackRF stuff seems to be the most effectively integrated SDR
> I just assume all the pros are here who already know all this stuff.
>
> --Chuck
>
> On Mon, Jul 31, 2017 at 10:22 PM, Dominic Spill <dominicgs at gmail.com> wrote:
>> On 30 July 2017 at 22:51, Chuck McManis <chuck.mcmanis at gmail.com> wrote:
>>>
>>> Every day I regret spending money on this LimeSDR unit, and the only way
>>> to talk to it is with 'SoapSDR' driving it through gr-osmosdr. Now why
>>> gr-osmosdr can't drive it directly? Who knows but still I thought I would
>>> rebuild gr-osmosdr from source and it dies horribly trying to build RTL
>>> stuff.
>>
>> Hi Chuck,
>>
>> We're not in a position to support LimeSDR on this mailing list, there's
>> no
>> link between the projects and I don't have access to the hardware.  I
>> don't
>> know if LimeSDR has a support channel, but I would recommend contacting
>> them
>> or other LimeSDR users as they will likely have experience with building
>> LimeSDR support for GNU Radio.
>>
>> Thanks,
>>   Dominic
> _______________________________________________
> HackRF-dev mailing list
> HackRF-dev at greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
>


More information about the HackRF-dev mailing list