Quoting Greg London <[EMAIL PROTECTED]> [Mar 04, 2002 14:19]:
> OK, URI.pm is installed.
> telling cpan.pm to "force" did the trick.
> something must have confused cpan.
>
> now I'm getting an error installing mod_perl.
>
> #>perl Makefile.PL APACHE_SRC=../apache_1.3.0/src
^^^^^^^^^^^^^
Are you really using this version?
> DO_HTTPD=1 USE_APACI=1 EVERYTHING=1
>
> everything looks good, except for this one line:
>
> (cd ../apache_1.3.0 && CC="gcc" CFLAGS=" -fno-strict-aliasing
> -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64"
> ./configure --activate-module=src/modules/perl/libperl.a
> --disable-rule=EXPAT)
> Configuring for Apache, Version 1.3.0
> + activated perl module (modules/perl/libperl.a)
> configure:Error: No such rule named 'EXPAT'
>
> anyone know what rule EXPAT is?
> apparently it prevents the makefile from getting
> created, because make fails.
If you really are using Apache 1.3.0, drop the EXPAT-related
config param. (Expat is an XML parser; recent versions of Apache
include expat-lite (I think) that can be compiled into the core.
If you are using any of Perl's XML modules that use Expat (like
XML::Parser) you'll want to disable Apache's Expat, because you
get unknown symbol errors and core dumps).
If you don't mean to be using such an ancient Apache, and grab a
recent tarball, then the --disable-rule=EXPAT will be recognized.
The URI.pm error makes me think you might also be using an old
version of mod_perl. Is that true?
(darren)
--
Capitalism interprets regulation as damage, and routes around it.
