I can reproduce this behavior; when going back to "master" everything is fine, switching to "next" brings up a window complaining about the pythonpath when trying to start grc. I never had set this path manually, the initial installation was done with Marcus' script and worked without manual changes.
Ralph. From: trond...@trondeau.com [mailto:trond...@trondeau.com] On Behalf Of Tom Rondeau Sent: Wednesday, 20 February, 2013 18:13 To: Ralph A. Schmid Cc: GNURadio Discussion List Subject: Re: [Discuss-gnuradio] build error with "next" branch On Wed, Feb 20, 2013 at 12:09 PM, Ralph A. Schmid <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
_______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
