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.
Let me also add, I'm grateful for your help. Thank you.
Steve D
The following comments were provided from Randy Kobes:
I think in general the problem "mod_perl.c" is not compatible with this
version of Apache.
means that mod_perl was compiled against a different set of Apache
sources than that used to build the server trying to load the mod_perl
module (assuming that the same compiler
is being used in building Perl, Apache, and mod_perl).
Just to clarify what came from where ....
- are you using a modperl-2.0 cvs snapshot from
http://cvs.apache.org/snapshots/modperl-2.0/?
- are you running Apache 2.0.43, compiled from the sources
httpd-2.0.43.tar.gz from
http://httpd.apache.org/dist/httpd/?
If so, does modperl-2.0 compile against these apache 2.0 sources
successfully?
--
best regards,
randy
