On Sat, Jun 26, 2010 at 10:29 PM, Josh Blum wrote:
> Somehow distutils solves this problem:
> http://docs.python.org/release/2.5.2/dist/node11.html
> If you figure out what its calling, perhaps we could port that the
> gnuradio build system
The code that does this can be seen here:
http://svn.pyth
Somehow distutils solves this problem:
http://docs.python.org/release/2.5.2/dist/node11.html
If you figure out what its calling, perhaps we could port that the
gnuradio build system
What would work is an m4 macro (or hook) that takes the list of python
bin scripts and creates new targets and insta
Thanks for both your replies. Regarding the PATH fix- in the situation
I'm looking to fix for myself and my users, I've got system python 2.4
from RHEL 5/CentOS 5 as /usr/bin/python and my python 2.5 as
/usr/bin/python2.5 (with python25 link). I suppose another choice would
have been to make it /us
On Sat, Jun 26, 2010 at 12:32:38PM -0500, Brett L. Trotter wrote:
> I'm just now getting to a gnuradio project and hadn't had much of a
> chance to dogfood my gnuradio RPM from my repo. Now that I'm getting to
> it, all of the examples scripts have #!/usr/bin/env python hardcoded at
> the top. I wa
I'm just now getting to a gnuradio project and hadn't had much of a
chance to dogfood my gnuradio RPM from my repo. Now that I'm getting to
it, all of the examples scripts have #!/usr/bin/env python hardcoded at
the top. I was thinking the build process (which already knows the
appropriate python)
