[mod_python] mod_python install fails

Jorey,
many thanks,  I'm now on the right path.
I've contacted CollabNet\requested the apxs that was compiled  with version 2.2.3
another question on this,
I've installed httpd-devel-2.0.52-28.ent  apache2-devel-2.0.46-1.72 during my hunt of apxs, should I remove these
packages from my server? also should I remove the default apache httpd-2.052-28.ent server
since I'm using 2.2.3?
this clean up should affect the RH server right?
 
Thanks,
Brian
 

________________________________

From: Jorey Bump [mailto:list at joreybump.com]
Sent: Wed 4/4/2007 12:43 PM
To: Brian McCann
Cc: mod_python at modpython.org
Subject: Re: [mod_python] mod_python install fails



Brian McCann wrote:

> here are all references ro apxs, there was no apxs wit Collabnet, that's
> why I installed apache2-devel to get it
> the version of apache that came with the RH install was 2.0.52 and the
> one with the collabnet install 2.2.3
> there is an apxs in /usr/sbin/ but when I run configure pointing to it,
> I get the output in bold below pointing to apache 2.0.52 not 2.2.3 are
> you saying that if I can get the apxs associated with apache version
> 2.2.3(the version CollabNet uses)mod_python will build succcessfully?

Yes, and I would even go so far as to say that you should use an apxs
that is created when the target Apache httpd installation is compiled.
In other words, it will be easiest to use an apxs that matches your
installation, not merely one that matches the version. I highly
recommend contacting CollabNet for support. It's trivial to include
apxs, so they have either overlooked it, or have a good reason not to do
so. If you explain your use case to them, they are in the best position
to provide further instructions.




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mm_cfg_has_not_been_edited_to_set_host_domains/pipermail/mod_python/attachments/20070404/6d9f2eda/attachment.html