Bunck, Peter [mailto:[EMAIL PROTECTED]] wrote:
> Thanks, but I've already tried that one.
> I am using the ibm c(c)-compiler for aix cxx. When looking for solutions
for
> this problem, I saw some
> references to that problem. So I completly recompiled and reinstalled
perl.
> There is only one c-compiler
> available, so some weird mixup is also not possible.
> As for the resulting error, when the string where should stand "cc" is
> empty, you get error message of
> the type:
> -I -I../../os/unix -I../../include -DAIX=43 -U__STR__
> -DAIX_BIND_PROCESSOR -qnogenpcomp -qnouse
> pcomp -I/usr/local/sources/php/php-4.0.4pl1
> -I/usr/local/sources/php/php-4.0.4pl1/main -I/usr/local/sources/php
> /php-4.0.1pl2/main -I/usr/local/sources/php/php-4.0.4pl1/Zend
> -I/usr/local/sources/php/php-4.0.4pl1/Zend -I/usr
> /local/sources/php/php-4.0.4pl1 -DUSE_EXPAT -I../../lib/expat-lite
> -DNO_DL_NEEDED `../../apaci` -c mod_perl.c
> /bin/sh: -I: not found.
I just ran into this problem as well.
Your problem is that the PERL_CC variable in the Makefiles is blank because
of an error in the configuration scripts.
Try this patch:
======== begin patch ==========
--- mod_perl-1.25.old/apaci/mod_perl.config.sh Thu Jun 7 08:15:28 2001
+++ mod_perl-1.25.new/apaci/mod_perl.config.sh Thu Jun 7 08:15:34 2001
@@ -107,8 +107,8 @@
# determine build tools and flags
#
-config_pm='-MApache::ExtUtils=%Config'
-#config_pm='-MConfig'
+#config_pm='-MApache::ExtUtils=%Config'
+config_pm='-MConfig'
perl_cc="`$perl_interp $config_pm -e 'print $Config{cc}'`"
perl_ccflags="`$perl_interp $config_pm -e 'print $Config{ccflags}'`"
perl_optimize="`$perl_interp $config_pm -e 'print $Config{optimize}'`"
======== end patch ==========
This undoes the following change:
http://www.apache.org/websrc/viewcvs.cgi/modperl/apaci/mod_perl.config.sh.di
ff?r1=1.20&r2=1.21
On this file:
http://www.apache.org/websrc/viewcvs.cgi/modperl/apaci/mod_perl.config.sh
An interesting interaction happens if you have a previous copy of mod_perl
installed (specifically the mod_perl package in Red Hat 7.1) when you try to
build. If mod_perl is already installed then the existing libperl.a is
brought from there instead of being compiled anew. No errors are shows an
the build fails. If you remove the existing mod_perl installation then these
errors stop the build process.
Doug, perhaps you could look into this and see why it broke and why it
sometimes builds successfully even with these errors?
David
