Thanks Andrew- good stuff. You've convinced me, I'm just going to bite the
bullet and rebuild :)
todd
On Sun, 24 Jun 2001, Andrew Ho wrote:
> Todd,
>
> Perl and mod_perl are separate entities altogether. Perl is the scripting
> language. mod_perl is an extension to Apache, which builds a Perl
> interpreter into the Apache webserver.
>
> The binary components are mostly separate, e.g. you could theoretically
> run Perl and mod_perl at different versions; the actual "perl" binary and
> the mod_perl extensions are separate.
>
> However, the Perl interpreter built into the Apache webserver, plus all
> the associated Perl modules that implement mod_perl's functionality,
> inherit all the characteristics of the Perl it was built against--bugs in
> the interpreter, language characteristics, or where to find libraries.
>
> In your case it sounds like your mod_perl is built for a different version
> of Perl. As several others have suggested, the best way is to rebuild
> mod_perl so it is built against your version of Perl.
>
> Another easier to do it would be to use your vendor's package system,
> for example if you are using RedHat or Debian, you may be able to find
> Perl and mod_perl packages (RPMs or whatnot) and install them to fix the
> versioning issues.
>
> I still recommend building it; for the base case, it's pretty easy to do.
> Follow the "all-in-one" directions in the mod_perl download and it usually
> Just Works.
>
> The symlinking and changing the @INC path may work, but this is a hacky,
> symptomatic solution at best.
>
> Humbly,
>
> Andrew
>
> ----------------------------------------------------------------------
> Andrew Ho http://www.tellme.com/ [EMAIL PROTECTED]
> Engineer [EMAIL PROTECTED] Voice 650-930-9062
> Tellme Networks, Inc. 1-800-555-TELL Fax 650-930-9101
> ----------------------------------------------------------------------
>
>
