grahamd at dscpl.com.au
Fri Jul 29 01:02:20 EDT 2005
Jim Popovitch wrote .. > On Fri, 2005-07-29 at 00:18 -0400, Jorey Bump wrote: > > > > Switching back and forth is likely to cause problems. To avoid this, > you > > will need to properly set configure options, > > mod_python does NOT support this with python2.x. You can define > $PYTHON_BIN prior to running configure, however configure doesn't > properly set the install section of the Makefile to the correct value > (it leaves it simply as "python"). Simply edit the generated "Makefile". You don't need to go and change the links in /usr/bin just to do the build/install. Ie., change the "Makefile" by hand to read: /usr/bin/python2.2 $(PY_STD_LIB)/compileall.py $(PY_STD_LIB)/site-packages/mod_python or whatever version as a appropriate. If you think editing generated makefiles is bad, edit "Makefile.in" and change: python $(PY_STD_LIB)/compileall.py $(PY_STD_LIB)/site-packages/mod_python to: @PYTHON_BIN@ $(PY_STD_LIB)/compileall.py $(PY_STD_LIB)/site-packages/mod_python Then rerun configure: PYTHON_BIN=/usr/bin/python2.2 ./configure > > customize the source code, > > crude and un-maintainable over time. Necessary if you insist on using an older version of code when the issue has been addressed in a newer version.