Yeah, Im here, I did it.
GRC wants python 2.5 (or above I say, but never tested). GRC is littered
with things from python2.5 that dont exist in the python2.4, relative
imports, some builtin functions, inline evaluation is somehow different.
Rather than become a burden on the configure, you just install grc with
whatever python gnuradio gets configured with. If its most systems,
python 2.5, it works, if its python 2.4, then nothing is hurt, grc just
dont work too well.
doing a configure option to disable grc in the case of python2.4 is not
too hard. Making it work with 2.4... thats another thing
-Jsoh
Eric Blossom wrote:
On Wed, Nov 12, 2008 at 03:06:16PM -0500, Achilleas Anastasopoulos wrote:
That's not a problem.
However, I have a bigger problem to deal with:
I am pushing for a university wide (UoMichigan) installation of all
gnuradio prereqs.
So far we have a working gnuradio installation that builds all required
packages except grc!
The university network has python 2.4 installed with all third-party
packages, and also pyhton2.5 interpreter.
Is there any way I can tell the configure file to use python 2.4
and then use the 2.5 interpreter to run grc?
If this is possible it will save a lot of effort as we will not have to
install all these new packages for 2.5 as well.
Thanks
Achilleas
Let's see what it takes to reduce GRC's dependency to Python 2.4 instead of 2.5.
Josh, are you out there? Comments?
Eric
_______________________________________________
Discuss-gnuradio mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
_______________________________________________
Discuss-gnuradio mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
