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 <
lwas...@ostatemail.okstate.edu> wrote:
> 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)?
>
>
> Logan Washbourne
> Electrical Engineering Graduate Student
> (Electromagnetics)
>
>
> On Mon, Aug 3, 2015 at 7:38 PM, West, Nathan <n...@ostatemail.okstate.edu>
> wrote:
>
>> Logan,
>>
>> For your case deleting inventory.dat would do the trick of effectively
>> resetting pybombs state (and if your done with an install rm the prefix)
>>
>> Mike,
>>
>> Pybombs is hiding the true error. Cmake failed for either VOLK or GNU
>> Radio. Try running pybombs again with -v -v
>>
>>
>> On Monday, August 3, 2015, <lwas...@ostatemail.okstate.edu> wrote:
>>
>>> Mike,
>>>
>>> When I ran into this problem, I had to reinstall pybombs. I think the
>>> problem lies in changing the installation prefix after installing pybombs.
>>>
>>> I'm sure there is another way to fix this, I just don't know what it is.
>>>
>>> When I reinstalled pybombs, I defined the installation prefix when the
>>> several prompts are asked at the beginning.
>>>
>>> Sent from my Cyanogen phone
>>>
>>> On Aug 3, 2015 4:39 PM, Mike Markowski <mike.ab...@gmail.com> wrote:
>>> >
>>> > 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]
>>> >
>>> > I first used
>>> >
>>> > apt-get install gnuradio
>>> >
>>> > Thinking better of it, I ran
>>> >
>>> > apt-get remove gnuradio
>>> > apt-get autoremove
>>> >
>>> > Then went with pybombs
>>> >
>>> > git clone git://github.com/pybombs/pybombs
>>> > cd pybombs
>>> > ./pybombs config [use install path /usr/local/gnuradio]
>>> > ./pybombs install gnuradio
>>> >
>>> > And after several tries continue to receive this error:
>>> >
>>> > [...many lines of install...]
>>> > Unpacking liblog4cpp5-dev (1.0-4) ...
>>> > Setting up liblog4cpp5-dev (1.0-4) ...
>>> > installation ok via: deb
>>> > Installing from source: gnuradio
>>> > Cloning into 'gnuradio'...
>>> > Checking connectivity... done.
>>> > Cloning into 'volk'...
>>> > remote: Counting objects: 5450, done.
>>> > remote: Compressing objects: 100% (10/10), done.
>>> > remote: Total 5450 (delta 2), reused 0 (delta 0), pack-reused 5440
>>> > Receiving objects: 100% (5450/5450), 1.54 MiB | 0 bytes/s, done.
>>> > Resolving deltas: 100% (3918/3918), done.
>>> > Checking connectivity... done.
>>> >
>>> > CC=gcc CXX=g++ cmake .. -DCMAKE_BUILD_TYPE=RelWithDebInfo
>>> -DCMAKE_INSTALL_PREFIX=/usr/local/gnuradio -DENABLE_DOXYGEN=OFF
>>> >
>>> > 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.
>>> >
>>> > Any hints as to what is going wrong?
>>> >
>>> > Thanks,
>>> > Mike
>>> _______________________________________________
>>> 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 mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
