I compiled mod_perl with USE_APXS=1 WITH_APXS=/usr/sbin/apxs EVERYTHING=1.
Among the configure output I got "PerlSSI.....................enabled",
which leads me to believe that the mod_include callback is enabled.
Does the fact that I am using all DSO modules have a bearing here?
Asside from
LoadModule includes_module modules/mod_include.so
LoadModule perl_module modules/libperl.so
AddModule mod_include.c
AddModule mod_perl.c
in httpd.conf and
AddType text/x-server-parsed-html .shtml
AddHandler server-parsed .shtml
in srm.conf, are there any other conf directives necessary to enable
the <!--#perl --> SSI directive?
I see in the thread "Re: mod_perl-1.21 and apache-1.3.9" that DSOs are
supposedly broken on systems with glibc-2.1.1 until apache-1.3.9. Could
this be the source of the trouble?
--Brian Haney
> -----Original Message-----
> From: Vivek Khera [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, November 09, 1999 8:17 AM
> To: Brian Haney
> Cc: [EMAIL PROTECTED]
> Subject: Re: mod_perl, perlSSI, and <!--#perl --> directive
>
>
> >>>>> "BH" == Brian Haney <[EMAIL PROTECTED]> writes:
>
> BH> I'm running apache 1.3.6 and mod_perl 1.21 on a Linux 2.0.36 kernel.
> BH> I have configured the server to parse .shtml files and standard SSI
> BH> directives from mod_include work, but I cannot get the <!--#perl -->
> BH> directive to work. All I get in the browser is
>
> How did you compile mod_perl? What did the output of the configure
> process report to you?
>
> --
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Vivek Khera, Ph.D. Khera Communications, Inc.
> Internet: [EMAIL PROTECTED] Rockville, MD +1-301-545-6996
> PGP & MIME spoken here http://www.kciLink.com/home/khera/
>
