Chris Jackson
christopher.jackson at gmail.com
Fri Feb 4 02:08:27 EST 2005
Point to the Apache version and Python version you want to use by doing: ./configure --with-apxs=/path/to/your/apache/bin/apxs \ --with-python=/path/to/your/python/python2.x Also, you may need to edit the LIBEXECDIR variable located in the Makefile to point to your Apache 2.x (/path/to/apache/modules) modules directory. ~= Chris =~ On Thu, 3 Feb 2005 22:51:03 -0800 (PST), Lawrence Bruhmuller <lbruhmuller at yahoo.com> wrote: > > Here is my dilemma: > > I am developing software to sit on top of RH Enterprise Linux (3.0 ES), and > furthermore sit on top of Python/Apache/mod_python. Business reasons > dictate RHEL as opposed to Fedora or other options. > > To support my application, I need mod_python 3.1.x, since I need the > mod_python.Session module. RHEL comes with mod_python 3.0.3. > > In addition, I also need python 2.3.x, and RHEL comes with 2.2.3. > > As I understand it, it is not a good idea to upgrade the system version of > python, as all kinds of other dependent programs could go awry. So I can > avoid this by just building python 2.3 from source, as the package > "python2.3", leaving "python" as is at 2.2.3. > > But if I do this, when I build mod_python from source, isn't it going to > build against "python" which is the old version? And hence I won't get what > I want? How I do I get mod_python built so that my "extra" python is used > at buildtime/runtime? > > Thanks much, > > Lawrence > > ________________________________ > Do you Yahoo!? > Yahoo! Search presents - Jib Jab's 'Second Term' > > > _______________________________________________ > Mod_python mailing list > Mod_python at modpython.org > http://mailman.modpython.org/mailman/listinfo/mod_python > > >
|