On Wed, Feb 20, 2013 at 12:09 PM, Ralph A. Schmid <ra...@schmid.xxx
<mailto:ra...@schmid.xxx>> wrote:
__
The build and build install worked just fine, but now the crazy
thing complains that the pythonpath is not set. Huh?! Why does a
new build influence a environment variable? And I have no idea how
to handle these things under Linux :-( So much to learn that I
never wanted to know :)
Ralph.
I assure you that the install did not change your environmental variables.
To set it, use 'export PYTHONPATH=[path]:$PYTHONPATH'. Some shells
want you to use 'set' instead of 'export.' The [path] is the path to
the installed Python packages; something like
/usr/local/lib/python2.7/dist-packages.
Tom
Indeed, and build-gnuradio actually tells you what your PYTHONPATH
should be set to for Gnu Radio support. The build-gnuradio script *could*
edit your .bashrc and set that variable for you, but doing so is
dangerous because .bashrc is, essentially, a *program*, which would involve
build-gnuradio somehow interpreting the semantics of said program,
and figuring out where to put the PYTHONPATH setting. Some hand-holding
is best left not done...
--
Marcus Leech
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
