Thank you for the info. I've uninstalled pybombs everywhere, so I
should be "clean" again.
I tried running your two easy_install commands and got an unexpected result:
jmat@jmat:~/Downloads$ easy_install --version
usage: easy_install [options] requirement_or_url ...
Marcus, I'll see if I can get our IT people's ear and figure out better
what is going on with sudo. It was indeed just a vanilla install of
16.04, and then IT did there mucking afterwards.
On 10/12/2016 03:55 PM, Marcus Müller wrote:
I can see that sudo
(However, I think there's a lot of upside to installing on a vanilla OS for
comparison, replicating your error on your IT-polluted OS, and forcing IT
to fix the problems they're imposing on you.)
On Thu, Oct 13, 2016 at 1:42 PM Nicholas McCarthy
I spoke with IT and I was mistaken on the "script" version of sudo. What
is really going on is that we use centrify's dzdo as sudo. They just
made a wrapper so that users can call sudo like usual and dzdo gets
called under the hood. So the sudo //should// be pretty normal.
I went to
You need to remove all versions of pip you previously installed and truly
start fresh with the curl command.
I recommend starting with a completely fresh install and never typing
"sudo." (This is assuming you DO have a reasonable python installed.)
Until you can run commands like pip install
Nick, A little more information.
I try to do the next step (add recipes) and I get the following:
jmat@jmat:~$ pybombs recipes add gr-recipes
bash: /usr/local/bin/pybombs: Permission denied
Looking at that binary, it has permissions 700. I chmod
Hello, all. In the /usr/share/uhd/images directory on the ARMv7
processor (p/o of the E310 and running Xilinx Linux) there are a number
of FPGA images for ostensibly other architectures besides the E310. If
another of these, say one of the several ones for an N210 device are
loaded into the
That's interesting... I was expecting it to prove your user saw a different
version of setuptools than running sudo. I think there's still evidence
that may be the case, but I'm not sure.
I think your best bet for building gnuradio on your non-vanilla machine is
to start from scratch
The test programs gr-blocks/tests/benchmark_nco.cc and
benchmark_vco.cc seems outdated. AFAICS, there are no
'nco' and 'fxpt_nco' classes in the namespace 'gr::blocks'.
Shouldn't these be patched like so:
--- a/gr-blocks/tests/benchmark_nco.cc 2015-12-16 21:39:46
they are on the SD Card just because the default method of getting them
downloads a whole bunch of images.
An FPGA image is 100% specific to exactly the FPGA and connections. The
N210's FPGA and the Zynq's PL aren't even similar; this can't work out,
you can't even successfully load
I am using Gnu Radio 3.7.8 with uhd 003.008.005 and umtrx v2.2. When I use
the attached GRC flowgraph I see random drops in the magnitude of the
transmission and also a carrier wave. Please see the link below for the
output. I searched on the internet but could not find anything. I used a
Mail list logo