[Discuss-gnuradio] Pybombs 2.1.0 test w/Ubuntu 16.04LTS
Greetings, Noticed in PyBOMBS 2.1.0Fresh and stock Ubuntu 16.04 on intel 4 core. https://github.com/apache/thrift.git. PyBOMBS.Fetcher - ERROR - [Errno 2] No such file or directory: '/home/gratcliff/gnuradio/.pybombs/inventory.yml' PyBOMBS.Packager.source - ERROR - Problem occurred while building package apache-thrift: Unable to fetch recipe apache-thrift PyBOMBS.install_manager - ERROR - Error installing package apache-thrift. Aborting. Gregory W. Ratcliff ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] divide_cc_impl.cc error in ::blocks
Greetings, I did a quick list search for this, but didn't see anything. Today I fired up a 64 bit Ubuntu 15.04 vm; let it does its normal updates, then "sourced" the shell script and ran pybombs update About an hour later after MUCH success the build failed.Anyone notice this recently? [ 12%] Building CXX object gr-blocks/lib/CMakeFiles/gnuradio-blocks.dir/divide_cc_impl.cc.o/home/gratcliff/gnuradio/src/gnuradio/gr-blocks/lib/divide_cc_impl.cc: In member function ‘virtual int gr::blocks::divide_cc_impl::work(int, gr_vector_const_void_star&, gr_vector_void_star&)’:/home/gratcliff/gnuradio/src/gnuradio/gr-blocks/lib/divide_cc_impl.cc:58:105: error: ‘volk_32fc_x2_divide_32fc’ was not declared in this scope _32fc(optr, numerator, (gr_complex*) input_items[inp], noutput_items * d_vlen); ^gr-blocks/lib/CMakeFiles/gnuradio-blocks.dir/build.make:4216: recipe for target 'gr-blocks/lib/CMakeFiles/gnuradio-blocks.dir/divide_cc_impl.cc.o' failedmake[2]: *** [gr-blocks/lib/CMakeFiles/gnuradio-blocks.dir/divide_cc_impl.cc.o] Error 1CMakeFiles/Makefile2:1957: recipe for target 'gr-blocks/lib/CMakeFiles/gnuradio-blocks.dir/all' failedmake[1]: *** [gr-blocks/lib/CMakeFiles/gnuradio-blocks.dir/all] Error 2Makefile:146: recipe for target 'all' failedmake: *** [all] Error 2PyBombs.Packager.source - ERROR - Build failed. See output above for error messages.PyBombs.Packager.source - ERROR - Problem occurred while building package gnuradio:Build failed.PyBombs.update - ERROR - Error updating package gnuradio. Aborting. Gregory W. Ratcliff ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] OOT idea
I was reminded about some of Michael Ossmann's work with yardstick one: Great Scott Gadgets - YARD Stick One | | | | | | | | | | | Great Scott Gadgets - YARD Stick OneYARD Stick One YARD Stick One is a sub-1 GHz wireless test tool controlled by your computer. YARD Stick One is available from: Hacker Warehouse (US) HakShop (U... | | | | View on greatscottgadgets.com | Preview by Yahoo | | | | | Has anyone considered creating an RFCAT "in a module" (for RTL or HackRFone)? Gregory W. Ratcliff ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Quickstart comments related to Ubunto 15.10 (out of the box)
Chris,
gnuradio-config-info --enabled-components
returned:
python-support;testing-support;volk;gnuradio-runtime;gr-ctrlport;*
thrift;gr-blocks;gnuradio-companion;gr-fec;gr-fft;gr-filter;gr-analog;gr-digital;gr-dtv;gr-atsc;gr-audio;*
alsa;*
oss;gr-channels;gr-noaa;gr-pager;gr-qtgui;gr-trellis;gr-uhd;gr-utils;gr-vocoder;gr-fcd;gr-wavelet;gr-wxgui;gr-zeromq
Gregory W. Ratcliff
From: Chris Kuethe <chris.kue...@gmail.com>
To: Gregory W. Ratcliff <n...@att.net>
Cc: GNURadio Discussion List <discuss-gnuradio@gnu.org>
Sent: Monday, April 11, 2016 11:07 PM
Subject: Re: [Discuss-gnuradio] Quickstart comments related to Ubunto 15.10
(out of the box)
...
> 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
> 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
>
> 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
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
--
GDB has a 'break' feature; why doesn't it have 'fix' too?
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Quickstart comments related to Ubunto 15.10 (out of the box)
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
gitExecuting pybombs install gnuradio osmosdr doesn't really work. It seems
like the last item on the list is attempted to build first.
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.
UHD worked (isn't support nice!).
Its not specifically mentioned in the quickstart that a fetch is required first.
Major problem
I fetched and installed gr-fcdproplusBuild 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.
Funcube Dongle Pro+ found as: plughw:1,0
Traceback (most recent call last):
File "/home/gratcliff/gnuradio/top_block.py", line 135, in
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
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.
Gregnz8r
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Ubunto 15.04 (right off the .iso) recipe for success
Chris,
THANKS. PIP seems happy.
List Python gurus I blew up with
gratcliff@ubuntu:~/gnuradio$ pybombs install gnuradio gr-osmosdr
Traceback (most recent call last):
File "/usr/local/bin/pybombs", line 9, in
load_entry_point('PyBOMBS==2.0.1', 'console_scripts', 'pybombs')()
File "/usr/local/lib/python2.7/dist-packages/pybombs/main.py", line 30, in
main
return dispatch() or 0
File "/usr/local/lib/python2.7/dist-packages/pybombs/commands/base.py", line
141, in dispatch
return get_cmd_dict(cmd_list)[args.command](cmd=args.command,
args=args).run()
File "/usr/local/lib/python2.7/dist-packages/pybombs/commands/install.py",
line 129, in run
self._check_if_pkg_goes_into_tree if not self.args.no_deps else lambda x:
bool(x in self.args.packages)
File "/usr/local/lib/python2.7/dist-packages/pybombs/dep_manager.py", line
56, in make_dep_tree
dep_trees[pkg] = self.make_tree_recursive(pkg, filter_callback)
File "/usr/local/lib/python2.7/dist-packages/pybombs/dep_manager.py", line
85, in make_tree_recursive
subtree = self.make_tree_recursive(dep, filter_callback)
File "/usr/local/lib/python2.7/dist-packages/pybombs/dep_manager.py", line
85, in make_tree_recursive
subtree = self.make_tree_recursive(dep, filter_callback)
File "/usr/local/lib/python2.7/dist-packages/pybombs/dep_manager.py", line
76, in make_tree_recursive
if not self.pm.exists(pkg):
File "/usr/local/lib/python2.7/dist-packages/pybombs/package_manager.py",
line 113, in exists
pkg_version = pkgr.exists(r)
File "/usr/local/lib/python2.7/dist-packages/pybombs/packagers/extern.py",
line 102, in exists
return self._packager_run_tree(recipe, self._package_exists)
File "/usr/local/lib/python2.7/dist-packages/pybombs/packagers/extern.py",
line 163, in _packager_run_tree
return satisfy_rule.ev(satisfy_evaluator)
File "/usr/local/lib/python2.7/dist-packages/pybombs/recipe.py", line 53, in
ev
return func(self.name, self.compare or ">=", self.version)
File "/usr/local/lib/python2.7/dist-packages/pybombs/packagers/extern.py",
line 172, in _package_exists
or (required_version is not None and not vcompare(comparator,
available_version, required_version)):
File "/usr/local/lib/python2.7/dist-packages/pybombs/utils/vcompare.py", line
34, in vcompare
return operators[cmp_op](LooseVersion(version_x), LooseVersion(version_y))
File "/usr/lib/python2.7/distutils/version.py", line 265, in __init__
self.parse(vstring)
File "/usr/lib/python2.7/distutils/version.py", line 274, in parse
self.component_re.split(vstring))
TypeError: expected string or buffer
Gregory W. Ratcliff
From: Chris Kuethe <chris.kue...@gmail.com>
To: Gregory W. Ratcliff <n...@att.net>
Cc: discuss-gnuradio <discuss-gnuradio@gnu.org>
Sent: Thursday, April 7, 2016 10:20 PM
Subject: Re: [Discuss-gnuradio] Ubunto 15.04 (right off the .iso) recipe for
success
I'm using 15.10 with little difficulty. I suppose I should spin up a 15.04 test
vm. On Apr 7, 2016 19:04, "Gregory W. Ratcliff" <n...@att.net> wrote:
Greetings,
Has anyone gone start to finish with 64 bit, desktop, 15.04, new pip and
pybombs 2+. ?
I would like to get back to enjoying gnuradio as quickly as possible.
Thank you,
Mr. Lazy.
Gregory W. Ratcliff
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Ubunto 15.04 (right off the .iso) recipe for success
Greetings, Has anyone gone start to finish with 64 bit, desktop, 15.04, new pip and pybombs 2+. ? I would like to get back to enjoying gnuradio as quickly as possible. Thank you, Mr. Lazy. Gregory W. Ratcliff ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Is cmake 3.0 really required now?
Old Pybombs14.04 LTS (you know stable stuff) Installing packages: * gr-fcdproplus Installing from source: gr-fcdproplus CC=gcc CXX=g++ cmake .. -DCMAKE_BUILD_TYPE=RelWithDebInfo -DCMAKE_INSTALL_PREFIX=/home/gratcliff/Downloads/target $config_opt CMake Error at CMakeLists.txt:32 (cmake_minimum_required): CMake 3.0 or higher is required. You are running version 2.8.12.2 cmake 3 won't likely come to and LTS packages for a while. Thanks in advance, Greg Gregory W. Ratcliff From: Jose Ruvalcaba <joruv...@gmail.com> To: discuss-gnuradio@gnu.org Sent: Monday, April 4, 2016 7:41 PM Subject: [Discuss-gnuradio] Trying to build a DVB-S2 LDPC decoder Hello,I am new to GNU radio and to SDR's and I am trying to implement a DVB-S2 LDPC decoder block that can be used with the LDPC DVB-S2 encoder available in GNU radio. I have been able to write an LDPC decoder which uses a 16,200 long parity check matrix used only for a DVB-S2 short frame, rate = 1/4 code. The problem is that when running my written block it's taking a long time to decode one iteration of data(about an hour long). I was wondering if anyone has any advice in how to go about writing code for FEC blocks, especially LDPC codes, which will be used in GNU radio and eventually in an SDR? In other words, are there certain libraries that should be used when trying to write FEC decoders in gnu radio? How could I make a GNU radio FEC block which takes in a codeword length 16,200, like the one in DVB-s2, to work in a USRP? Is it smart to make my large (12960 x 16,200) parity check matrix using the standard 'vector' library in C++? Any advice, tips and suggestions will be greatly appreciated.Thanks, Jose ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Hardware "jitter", particularly USB
GnuRadio community, I have been using various hardware interfaces to gnuradio lately.In the simplest example, I noticed an issue with Funcube Pro Plus with broadcast wideband FM (about 4 GRC blocks) whereby it would consistently underflow, even though every rate appeared to be perfect. A crude but effective fix has been to interpolate by 500, decimate by 499. I occasionally notice a similar problem with DVB modules, never with Hermes. This has caused me to wonder if some subtle error has crept into OSMOCOM or the Funcube module has a timing error (that had been masked previously by OSMOCOM). Am I alone in this (in which case I will look closely at usb/audio/pc hardware)? Thanks in advance, GregNZ8R Gregory W. Ratcliff ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Pybombs and apache thrift help request
I believe the recipe for thrift needs an update: Looking at the recipe .lwr I see: depends: libtool automake gcc boost bison flex libevent python ssl category: baseline source: git://https://github.com/apache/thrift.git gitrev: dd89dce8 inherit: bootstrapautoconf Looking for this rev below shows no revs that match. https://github.com/apache/thrift/release I am having trouble tracking down which version we need and where or why it was pulled. Which rev do we like? Thanks in advance, Gregnz8r (yes another gnu-ham) Gregory W. Ratcliff ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] path issue with pybombs env
Greetings all, Could someone confirm this as a problem? Base system: Win 7VM: VMPlayer free v10OS: Ubunto v14.04ltspybombs download: git clone git://github.com/gnuradio/pybombs We have an invalid path entry for this configuration: export PATH= lots of correct stuff...then /usr/lib/x86_64-linux-gnu/qt4/bin::/usr/lib64/qt4/bin/ bash was upset.I noticed QT4 bin stuff here: :/usr/lib64/qt4/bin/ Quick edit (in my case usr/gratcliff) fixed things: # WARNING: This file is auto-generated by pybombs, any manual changes to it may be overwritten! export PATH=/home/gratcliff/Downloads/target/bin/:/home/gratcliff/Downloads/target/bin/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/lib/x86_64-linux-gnu/qt4/bin: Thanks, Gregnz8r ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] SDR/USRP devices
Marcus, So everyone is thinking it: Show a little discuss-gnuradio love and set up an educational one time group buy. I have had SDR envy for some time; stuck with RTL/Hermes/Funcube, when what I really need is some new Ettus hardware. It NEVER shows up on Ebay it seems. Think how many less I can't get gnuradio to work with insert inferior stuff here; can't you guys do this for me on this discussion list responses you would have to create. Greg From: Marcus Müller marcus.muel...@ettus.com To: Pedro Gabriel Adami pedrogabriel.ad...@gmail.com; discuss-gnuradio@gnu.org Sent: Monday, August 17, 2015 2:27 PM Subject: Re: [Discuss-gnuradio] SDR/USRP devices Hi Pedro, You will, as for any device, need to figure out what you need, specification-wise. I'm obviously a bit biased, but no one else might even be able to help you unless you wrote some numbers: frequencies you're interested in, bandwidth you want to sample at once, stability, available interfaces, cost range etc. Best regards, Marcus Am 17. August 2015 20:13:38 MESZ, schrieb Pedro Gabriel Adami pedrogabriel.ad...@gmail.com: Hello, I've been searching a lot about SDR and USRP devices to purchase. All I need is a board with a receiver port (transmitter is not important for now) and it's necessary to be compatible with Gnuradio. There are some options, but I don't have experiency or enough knowledge to choose one of them (I don't know the brands, if they are reliable, etc). I found RTL2838U/R820T2. Is it good? What are the other boards that you know? Sorry about the questions, but I'm kind of new here. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Free IEEE tutorial
Below is a free (to IEEE members) tutorial on wide bandwidth signal analysis. Let me know If you guys consider this kind of thing spam and but me being curious always appreciate a few diversions from time to time. We all could learn something from this I expect. Greg Gregory W. Ratcliff ***http://event.on24.com/r.htm?e=1026616s=1k=64D655E7978210FA93FA3793C48A82E7 | Error Vector Magnitude measurements fit for 5G | | DESCRIPTION: Error vector magnitude, EVM, measurements have been the mainstay of modulation performance analysis for more than twenty years. Each new technology has defined a specific measurement to suit the characteristics of the physical layer signal. The interest in signals for 5G that are much wider bandwidth, operating at much higher frequencies means it’s time to draw a comparison between the different waveforms and the impact on the measurement of EVM. This presentation reviews what an EVM measurement is and what it can tell us about the device being measured. A combination of real life and simulated examples are used, with single and multi-carrier waveforms having bandwidths of 20 MHz – 2 GHz, to demonstrate the impact of a variety of signal impairments, including broadband noise and phase noise. The examples will show how to make measurements that give the expected, and consistent results. | ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Embedded WG
Philip, Your email likely roused some lurkers. One, anyway.I have liked the spotlight method for new projects.Put up a couple dozen little projects and have people pick up the project they are suited for and have them deliver.If they don't not much is lost, if they are fast, they pick up the next. How can I help? How can I learn what needs started/finished? 1) r-pi2 (I keep a couple for experimenting here) Jetson (Booted it, smiled at the performance, did nothing else) Gregnz8r From: Philip Balister phi...@balister.org To: Discuss-Gnuradio@Gnu. Org discuss-gnuradio@gnu.org Sent: Monday, June 15, 2015 4:54 PM Subject: [Discuss-gnuradio] Embedded WG Recently I was asked how people can help with the embedded working group. Currently, I a very happy with our support for Zynq based boards. I've put together a list othings I think we can improve. Embedded Working goals: 1) Expand hardware support - Wandboard - r-pi2 - Jetson - insert your favorite here 2) More stuff in meta-sdr - sdr shiny - OOT modules 3) Performance improvements - Need to better understand bottlenecks 4) Killer apps! - Verify gnuradio examples 5) Expand participation The first couple of items involve OpenEmbedded work, finding BSP layers for boards, testing them, working to get them creating easy to use images, and writing recipes for more OOT modules. For the next year, I'd like to get more people actually using the infrastructure we have. I'd like to get a list of gnuradio apps together and start validating they run on various embedded platforms. Even better, writing gnuradio applications designed to run well on embedded systems. I'd also like some feedback on who would attend a WG call sometime in the next few weeks. Philip ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] FCDproplus: FunCumb Dongle V2.0 soundcard found but not controlpart
There were a few threads a while back where this problem was discussed.It seemed the issue was never debugged, just disappeared after a clean install. About as clean as I know to make it: Running Ubuntu 14.04 LTS from wiped clean (as of 5/4/2015), 64 bit desktopDownloaded and installed today's PybombsInstalled osmocom, rtl and gr-fcdproplu RTL and osmocom work fine. Completed with a Pybombs update Rumors else indicate this is a UDEV permissions issue. Ideas? Gregnz8r ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] HermesNB with Pybombs
Tom, Heard your talk on this work. Went digging around in the new Pybombs list but didn't notice anything that looked HPSDR-like. Before I go to TAPR subversion could you give us a pointer to the latest version for the Everyone wants to brag about their progress before Dayton weekend. Gregnz8r ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Pybombs first journey ( should we create a 101 and troubleshooting page?)
Greetings, As I asked last week (thanks for the responses); I wanted to begin using Pybombs and get on board with the new work. I decided to start with a clean slate. Downloaded and Installed Ubunto 12.04 Desktop LTS (Long Term Supported)-did not choose developer thinking Pybombs will go get what it needs.Downloded and installed Pybombs into my ~/home/x/pybombs -git clone git://github.com/pybombs/pybombs -cd pybombs -./pybombs install gnuradio A few hours later I ran (hurts to have a 1meg link in rural america and 240m at work) ./pybombs env Then: I did a ./pybombs list and had gnuradio and lots of libs (Yea!). I went looking for setup_env.sh and could not find it. The only executable .sh is named jenkins.shI went looking for gnuradio-companion with find (from /) and did not find it. So I went to bed. I keeping pretty good notes, so will publish the findings here or on the wiki later.if you have notes I'm glad to add those too... (my email address is my callsign @att.net) Looking for some advice for this evening's work. Gregnz8r ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Moving from an apt-get (Ubunto) install to Pybombs
Greetings, Long time lurker--daily user, but now faced with a decision. I have noticed the fine work with Pybombs and picked up a more hardware and thought to myself:Hey, now is time to bite the bullet is start using Pybombs I don't want that bullet to shoot me in the foot (sorry). Question: What is the safest method to switch to Pybombs for a working installation?My thoughts were to 1. Remove what I can manually and start over2. Tell Pybombs to install into the ubunto /user/local/blah dirs. Gregnz8r ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
