I am also unable to compile statically. I am configuring against
Apache 1.3.19 on Solaris 2.7. I just installed perl 5.6 with
a whole slew of modules.

Here is how I configure apache:
--prefix=/usr/local/apache \
--enable-module=all \
--enable-shared=max \
--activate-module=src/modules/php4/libphp4.a \
--activate-module=src/modules/perl/libperl.a \
--disable-module=auth_db

Note: If I do not activate the perl module, it compiles fine.

I build and install mod_perl as follows:
perl Makefile.PL
yes, to configure against ../apache-1.3.19/src
no, to shall I build apache
make
make install

I then manually look in apache/src/modules/perl for the new code.

Here is what I get when I try and compile apache:

RSION=\"1.25\"   -I./os/unix -I../../include    -c  mod_perl_opmask.c
sh: ../apaci: not found
*** Error code 1
make: Fatal error: Command failed for target `mod_perl_opmask.o'
Current working directory /usr/local/src/apache_1.3.19/src/modules/perl
*** Error code 1
make: Fatal error: Command failed for target `all'
Current working directory /usr/local/src/apache_1.3.19/src/modules
*** Error code 1
make: Fatal error: Command failed for target `subdirs'
Current working directory /usr/local/src/apache_1.3.19/src
*** Error code 1
make: Fatal error: Command failed for target `build-std'
Current working directory /usr/local/src/apache_1.3.19
*** Error code 1
make: Fatal error: Command failed for target `build'

Note: This exact procedure works flawlessly on SuSe and Red Hat linux.


Anyone have any ideas?

THanks,
CC



> Stead of DSO why don't you compile
> statically.
> 
> On Tue, Apr 24, 2001 at 02:47:55PM -0700, Mod-Perl List wrote:
> > 
> > 
> > I am trying to build mod_perl 1.25 as a DSO on Solaris 2.7
> > and when I execute perl Makefile.PL, it says I will probably
> > get core dumps and to upgrade to perl 5.6. I am running
> > Perl 5.005_03, the latest considered stable on Solaris 2.7. I
> > cannot upgrade to 5.6 due to heavy perl code already on this
> > machine.
> > 
> > Can anyone point me in the right direction?
> > 
> > Thanks,
> > CC
> 

Reply via email to