Re: [Discuss-gnuradio] Problem using GRC when executing the grc examples

On Wed, Mar 3, 2010 at 10:06, Josh Blum wrote: > For the future: I just pushed a branch that will generate the python file in > your system's temp directory should the default directory be read-only. This has been merged into master. Johnathan ___ D

Re: [Discuss-gnuradio] Problem using GRC when executing the grc examples

Just to clarify, this problem with the examples has nothing to do with .bashrc. Nevertheless, it is good to understand the .bashrc when working on a unix system (specifically one with bash). For your installation, just save the .grc file to a writable directory. For the future: I just pushed a

Re: [Discuss-gnuradio] Problem using GRC when executing the grc examples

> You need to access .bashrc with super user rights. > Shouldn't ~/.bashrc be a user- override of the global /etc/bashrc (in ubuntu /etc/bash.bashrc) ? For instance if I want to change the promt to something like "[hh.mm.ss]:usern...@host >$" instead of the default one, I'd put those changes in m

Re: [Discuss-gnuradio] Problem using GRC when executing the grc examples

Makmur, .bashrc is just a convenient way to set environment variables and aliases when you open a terminal. if setting theose environment variables (BOOST_PREFIX and LD_LIBRARY_PATH) before you run grc from the command line fixes your problem, then you would want to add them to your .bashrc file.

Re: [Discuss-gnuradio] Problem using GRC when executing the grc examples

The error says: > Generating: "/usr/share/gnuradio/examples/grc/simple/ber_sim.py" > Generate Error: [Errno 13] Permission denied: > '/usr/share/gnuradio/examples/grc/simple/ber_sim.py' GRC generates the python files in the directory that the .grc file is found. Since the examples are installed

Re: [Discuss-gnuradio] Problem using GRC when executing the grc examples

You need to access .bashrc with super user rights. Open a terminal, and type the following commands: cd ~ sudo gedit .bashrc This will prompt for your password, then open .bashrc in an editable mode. A less recommended method of getting around this, would to change the access rights to .basrc w

Re: [Discuss-gnuradio] Problem using GRC when executing the grc examples

Makmur Hidayat wrote: > > > 2010/3/3 Mattias Kjellsson m...@kth.se > > > $chmod +w .bashrc > would make the above file writable. But ".bashrc" shouldn't really be > r/o, should it? This file should be readable by everyone, and > read/writable for the owner

Re: [Discuss-gnuradio] Problem using GRC when executing the grc examples

2010/3/3 Mattias Kjellsson m...@kth.se > > $chmod +w .bashrc > would make the above file writable. But ".bashrc" shouldn't really be > r/o, should it? This file should be readable by everyone, and > read/writable for the owner. At least in my experience. > Thanks Mattias, After I did--> $chmod

Re: [Discuss-gnuradio] Problem using GRC when executing the grc examples

Makmur Hidayat wrote: > Then I try to add the following to .bashrc > > export BOOST_PREFIX=/opt/boost_1_37_0 > export LD_LIBRARY_PATH=$BOOST_PREFIX/lib > > But I can not do that because .bashrc is read only. > > Therefore how to solve the problem? $chmod +w .bashrc would make the above file wri