On Fri, 3 Jan 2003, Steve Davis wrote:
> Randy,
>
> All of what I've done, in the form of compiling software, has been done
> on the same computer and with the same release of the RH. So, there is
> nothing for which I'm doing to distinctly change which compiler is being
> used between the compilations of the packages.
>
> As best as I can recall, the answer is 'yes' to the last three questions
> you asked. 1) Everything compiles successfully. 2) The edition of
> mod_perl was obtained from cvs.apache.org while the Apache was from the
> distribution source repository. 3) The various release numbers for the
> packages where the most current; hence, 2.0.43 of Apache and 2.0 for
> mod_perl.
>
> Maybe there is some difference between the distribution and CVS versions
> of Apache. Perhaps, the next step will be to match packages via
> obtaining CVS editions from both packages and see what happens then.
> This shouldn't take to long. I'll give it a shot and provide an update.
This is strange ... I just tried, on a RedHat 7.1 system, the
cvs modperl-2.0 sources compiled against
Server version: Apache/2.0.43
built using stock httpd-2.0.43 sources, and it went fine. You
shouldn't have to use the cvs apache sources. mod_perl was built as
perl Makefile.PL MP_AP_PREFIX=/usr/local/httpd MP_INST_APACHE2=1
where the httpd binary is installed under /usr/local/httpd/bin.
One thought ... Some Linux distributions come with their own
Apache server, which may be in a different location than the
Apache 2.0.43 you built and installed. Are you sure that the
mod_perl you built is being used with your Apache-2.0.43
specified under MP_AP_PREFIX?
--
best regards,
randy
