discuss-gnuradio
[Top][All Lists]
Advanced

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

Re: [Discuss-gnuradio] Quickstart comments related to Ubunto 15.10 (out


From: Chris Kuethe
Subject: Re: [Discuss-gnuradio] Quickstart comments related to Ubunto 15.10 (out of the box)
Date: Tue, 12 Apr 2016 12:16:59 -0700

git is now a build-essential, though it may take some time for pip to
be updated with the latest version with this change.

On Mon, Apr 11, 2016 at 8:07 PM, Chris Kuethe <address@hidden> wrote:
> On Mon, Apr 11, 2016 at 6:32 PM, Gregory W. Ratcliff <address@hidden> wrote:
>> Guys,
>>
>> Well done on the new pybombs, works mostly.
>>
>> I installed and tested these on a whitebox PC, VMware VM and Dell 4500 quad
>> core laptop.
>>
>> All systems used the .iso image installation from a clean system (formatted
>> partition).
>> apt-get update
>>
>>
>> ***********
>> Minor findings:
>>
>> The Git is required to be installed.  Easy to fix with apt-get install git
>
> Thanks for the report. I've submitted a PR which adds git to the build
> essentials.
>
>> Executing pybombs install gnuradio osmosdr doesn't really work.  It seems
>> like the last item on the list is attempted to build first.
>
> For all of my comments below, could you post a build log someplace
> illustrating the problem, as I have not seen these behaviors on my
> builds this week (also using a U15.10 host).
>
> I don't see what's wrong in building from the bottom up as long as
> when I say "pybombs install gqrx"  gnuradio, uhd, airspy, rtlsdr, and
> hackrf all build before gr-osmosdr uses them to produce a working GQRX
> binary.
>
>> I executued pybombs install gnuradio as a stand alone and about an hour
>> later I had a working gnuradio system.
>>
>> Then pybombs install osmosdr worked.
>
> There isn't any module called "osmosdr". There is "osmo-sdr" and
> "gr-osmosdr". Are you saying that "pybombs install gr-osmosdr" failed
> to compile? If so, that means there is a missing dependency
> declaration that we should fix.
>
>> UHD worked (isn't support nice!).
>
> Indeed. It saves me a huge amount of time to use the PPA.
>
>> Its not specifically mentioned in the quickstart that a fetch is required
>> first.
>
> Can't reproduce. What part required a fetch? On my systems I'm able to
> "pybombs install ____" and everything necessary happens; apt-get, git,
> gcc, etc. as appropriate.
>
>> ********
>> Major problem
>>
>> I fetched and installed gr-fcdproplus
>> Build and install worked without error.
>> Upon execution on a test flowgraph the long time swig bug/error came back
>> (see below the ***)
>> Anyone remember what the fix for this was?  Its not in anything I could find
>> on the list.
>
> Your error message mentions ControlPort. Could you check if
> gr-ctrlport is installed with
>     gnuradio-config-info --enabled-components
>
>> Funcube Dongle Pro+ found as: plughw:1,0
>> Traceback (most recent call last):
>>   File "/home/gratcliff/gnuradio/top_block.py", line 135, in <module>
>>     main()
>>   File "/home/gratcliff/gnuradio/top_block.py", line 123, in main
>>     tb = top_block_cls()
>>   File "/home/gratcliff/gnuradio/top_block.py", line 75, in __init__
>>     self.fcdproplus_fcdproplus_0 = fcdproplus.fcdproplus("",1)
>>   File
>> "/home/gratcliff/gnuradio/lib/python2.7/dist-packages/fcdproplus/fcdproplus_swig.py",
>> line 105, in make
>>     return _fcdproplus_swig.fcdproplus_make(device_name, unit)
>> RuntimeError: FunCube Dongle  V2.0 soundcard found but not controlpart.
>>
>>>>> Done (return code 1)
>> ^CTraceback (most recent call last):
>>   File "/home/gratcliff/gnuradio/bin/gnuradio-companion", line 130, in
>> <module>
>>     main()
>>   File "/home/gratcliff/gnuradio/bin/gnuradio-companion", line 126, in main
>>     ActionHandler(args, Platform())
>>   File
>> "/home/gratcliff/gnuradio/lib/python2.7/dist-packages/gnuradio/grc/gui/ActionHandler.py",
>> line 78, in __init__
>>     gtk.main()
>>
>> Next steps move on to Hermes, dump 1090 and a few others I have built from.
>>
>> Greg
>> nz8r
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Discuss-gnuradio mailing list
>> address@hidden
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>
>
>
>
> --
> GDB has a 'break' feature; why doesn't it have 'fix' too?



-- 
GDB has a 'break' feature; why doesn't it have 'fix' too?



reply via email to

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