I use gentoo at home and have no difficulty keeping gnuradio up to date.
At work we’re on a standalone network (no internet) so occasionally
bring
computers home to update them. Lately, I’ve been having trouble with
pybombs. Using a freshly installed ubuntu 15.04, then doing an
apt-get update
apt-get upgrade [not sure the update was necessary]
Configuring: (100%)
[==========================================================]
Configuration failed. Re-trying with higher verbosity.
make: *** No targets specified and no makefile found. Stop.
Build failed. See output above for error messages.
Thanks, Nathan, and all who replied publicly and privately,
The problem seems to be that I had installed Anaconda (from Continuum
Analytics) which does not include Cheetah by default. It does exist,
however, in the python tree installed by ubuntu, and that seemed to
confuse
things. I installed Cheetah within the anaconda tree and I believe all
is
well. I can say for sure when compiling completes!
Thanks Nathan. Should I have to use sudo when using pybomb commands, now
that the installation prefix is outside of my home directory(because I
now
I have to use sudo when using pybomb commands)?
You only have to use sudo with pybombs if you don’t have write
permission
to your prefix. In general it’s best to avoid using sudo and pybombs
together if possible (with the exception of when pybombs asks you for
sudo
password when using apt-get install). You can either set the prefix to
somewhere your user normally has write access to (typically your home
directory), or alter permissions of your prefix. As an example, if you
were
setting your prefix to /opt/gnuradio/pybombs-v3.7.8 the least obtrusive
way to do this is
sudo mkdir -p /opt/gnuradio/pybombs-v3.7.8 # assuming your user
doesn’t
have write access to /opt/gnuradio you need sudo to mkdir
sudo chown myusername:mygroupname /opt/gnuradio/pybombs-v3.7.8
./pybombs install gnuradio
In practice I usually make a group on my machines called ‘developer’ and
add my user to it, then give the developer group ownership or write
access
(depends on what I feel like when I set up a new machine) to /opt. That
lets me write whatever to /opt without sudo (don’t forget you need to
login
after adding your user to group for it to take effect). The same
principle
can be used with /usr/local or any other directory, but IMHO you should
at
least make your work an extra layer deep so you can just rm -rf the
whole
prefix (without root!) and not have much to worry about damaging.
Cheers,
Nathan
On Mon, Aug 3, 2015 at 9:15 PM, Washbourne, Logan <
So I changed the install prefix to /home/username/thesis/target and then
deleted the inventory.dat file and removed the previous install prefix
folder(this was usr/local, but it actually ended up in usr/local/share,
I’m
thinking this was a problem because I think there are lingering files).
I’m
having problems now, I can’t remove or update any packages, it states
that
there is not an inventory file so it creates an empty one and then
states
there is nothing to do. Is there a way to have it generate a new
inventory
file? I can’t install any packages because they seem to still be in the
pybombs folder. Do you have any advice Nathan?
My initial reasoning for changing the install prefix to usr/local/ was
to
enable me to create my own OOT modules and build the tutorial examples.
When pybomb’s install prefix was in my home directory it kept throwing
an
error about the CMake files. I tried to change the install prefix
locations
within those CMake files but that didn’t seem to fix my problems.
I’m really starting to learn that a little knowledge can be a pretty
dangerous thing haha.
My problem was not being able to use the gr-tutorials examples if I
didn’t
have Gnuradio installed in /usr/local, but then I realized that the
gr-tutorials was also a pybombs recipe so I used pybombs to install it
and
everything worked out great! Thank you both for helping me learn how to
move my install prefix around and about proper folder locations.
