You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by Michael <mi...@gmx.net> on 2004/03/18 17:43:41 UTC

apache + mod_perl + mod_php fails

Hello,

I have problems compiling apache under mac os x. I had no problems 
without php but with php it doesn't work. Furthermore i need 
mod_rewrite. I consulted docs at perl.apache.org and the install-guide 
in practical mod_perl. What i did starting in /usr/local/src:

This is a simple installation scenario of the mod_perl and mod_php in 
Apache server:
1.  Configure Apache.
cd apache_1.3.29
sudo ./configure --prefix=/usr/local/apache --with-layout=Apache
2.  Build mod_perl.
cd ../mod_perl-1.29
sudo perl makefile.PL \
APACHE_SRC=../apache_1.3.29/src \
NO_HTTPD=1 \
USE_APACI=1 \
PREP_HTTPD=1 \
EVERYTHING=1
sudo make
3.  Build mod_php.
cd ../php-4.3.4
sudo ./configure --with-apache=../apache_1.3.29 \
--with-mysql --enable-track-vars
sudo make
sudo make install
4.  Build Apache:
cd ../apache_1.3.29
sudo ./configure \
--prefix=/usr/local/apache \
--with-layout=Apache \
--activate-module=src/modules/perl/libperl.a \
--activate-module=src/modules/php4/libphp4.a \
--enable-module=rewrite \
--enable-shared=rewrite
sudo make

after this make i get:

ld: warning -L: directory name (../modules/php4) does not exist
ld: warning -L: directory name (../../modules/php4) does not exist
ld: Undefined symbols:
_actions_module
_include_module
_log_config_module
make[2]: *** [target_static] Error 1
make[1]: *** [build-std] Error 2
make: *** [build] Error 2

but this php4-dir is there! So what do i do wrong? Everything else 
yields no errors and as said before works fine without php.
I can only find docs concerning either php or mod_perl. The practical 
mod_perl book an the mod_perl website are the only sources i found that 
mention this kind of installation.

Please help me getting this thing up and running!


-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html


Re: apache + mod_perl + mod_php fails

Posted by Stas Bekman <st...@stason.org>.
Michael wrote:
> So i reran ranlib and configure and make as told in the instructions on 
> mod_perl website. I continue to get:
> <snip>
> ld: warning -L: directory name (../modules/php4) does not exist
> ld: warning -L: directory name (../../modules/php4) does not exist
> ld: warning prebinding disabled because dependent library: 
> /usr/lib/libdl.0.dylib is not prebound
> ld: Undefined symbols:
> _actions_module
> _include_module
> _log_config_module
> make[2]: *** [target_static] Error 1
> make[1]: *** [build-std] Error 2
> make: *** [build] Error 2
> </snip>
> 
> Shall i post the complete output of make? Where do i get help on this 
> issue? Building apache with modperl and modphp and modwrite is possible?

what about this question?

>> can you build mod_php4 on 
>> its own? I'd try to do that first, as the cause of the problem could 
>> be in the mod_php land.

__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html


Re: apache + mod_perl + mod_php fails

Posted by Michael <mi...@gmx.net>.
So i reran ranlib and configure and make as told in the instructions on 
mod_perl website. I continue to get:
<snip>
ld: warning -L: directory name (../modules/php4) does not exist
ld: warning -L: directory name (../../modules/php4) does not exist
ld: warning prebinding disabled because dependent library: 
/usr/lib/libdl.0.dylib is not prebound
ld: Undefined symbols:
_actions_module
_include_module
_log_config_module
make[2]: *** [target_static] Error 1
make[1]: *** [build-std] Error 2
make: *** [build] Error 2
</snip>

Shall i post the complete output of make? Where do i get help on this 
issue? Building apache with modperl and modphp and modwrite is 
possible?

Thanks for Your help
Michael

Am 18. Mär 2004 um 20:55 schrieb Stas Bekman:

> Michael wrote:
>> Hello Ged,
>> I copied all files to my ~ and repeated all setps. After make in 
>> point  4 i now get:
>> <snip>
>> ** A test compilation with your Makefile configuration
>> ** failed.  The below error output from the compilation
>> ** test will give you an idea what is failing. Note that
>> ** Apache requires an ANSI C Compiler, such as gcc.
>
> So much better when you show the real build output ;)
>
>> ======== Error Output for sanity check ========
>> cd ..; gcc  -DDARWIN -DMOD_PERL -DUSE_PERL_SSI -pipe -fno-common  
>> -DPERL_DARWIN -no-cpp-precomp -fno-strict-aliasing -DUSE_EXPAT  
>> -I./lib/expat-lite `./apaci` -I.  
>> -I/usr/local/lib/perl5/5.8.3/darwin-2level/CORE    -o helpers/dummy  
>> helpers/dummy.c   -Lmodules/php4 -L../modules/php4 
>> -L../../modules/php4
>
> as you can see mod_php's configure has pushed:
>
>   -Lmodules/php4 -L../modules/php4 -L../../modules/php4
>
> don't ask us why, ask the php guys. ;)
>
>> -lmodphp4      -lm       -L/usr/local/lib  
>> /usr/local/lib/perl5/5.8.3/darwin-2level/auto/DynaLoader/DynaLoader.a 
>>  -L/usr/local/lib/perl5/5.8.3/darwin-2level/CORE -lperl -ldl -lm -lc
>> ld: warning -L: directory name (../modules/php4) does not exist
>> ld: warning -L: directory name (../../modules/php4) does not exist
>
> so these are just warnings, ignore them.
>
>> ld: table of contents for archive: modules/php4/libmodphp4.a is out 
>> of  date; rerun ranlib(1) (can't load from it)
>
> do you think that's the cause of the error? can you build mod_php4 on 
> its own? I'd try to do that first, as the cause of the problem could 
> be in the mod_php land.
>
>> ld: warning prebinding disabled because dependent library:  
>> /usr/lib/libdl.0.dylib is not prebound
>
> i'm not a darwin user, so i'm not sure whether this is important, but 
> as it says it's a warning, let's hope that it's harmless.
>
>> make: *** [dummy] Error 1
>
>
>>> 73,
>>> Ged.
>>
>> what does 73 stand for?
>
> good bye in morse:
> http://www.envf.port.ac.uk/illustration/z/hig/71to80/73/jb/73.htm
>
> __________________________________________________________________
> Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
> http://stason.org/     mod_perl Guide ---> http://perl.apache.org
> mailto:stas@stason.org http://use.perl.org http://apacheweek.com
> http://modperlbook.org http://apache.org   http://ticketmaster.com
>


-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html


Re: apache + mod_perl + mod_php fails

Posted by Stas Bekman <st...@stason.org>.
Michael wrote:
> Hello Ged,
> 
> I copied all files to my ~ and repeated all setps. After make in point  
> 4 i now get:
> <snip>
> ** A test compilation with your Makefile configuration
> ** failed.  The below error output from the compilation
> ** test will give you an idea what is failing. Note that
> ** Apache requires an ANSI C Compiler, such as gcc.

So much better when you show the real build output ;)

> ======== Error Output for sanity check ========
> cd ..; gcc  -DDARWIN -DMOD_PERL -DUSE_PERL_SSI -pipe -fno-common  
> -DPERL_DARWIN -no-cpp-precomp -fno-strict-aliasing -DUSE_EXPAT  
> -I./lib/expat-lite `./apaci` -I.  
> -I/usr/local/lib/perl5/5.8.3/darwin-2level/CORE    -o helpers/dummy  
> helpers/dummy.c   -Lmodules/php4 -L../modules/php4 -L../../modules/php4

as you can see mod_php's configure has pushed:

   -Lmodules/php4 -L../modules/php4 -L../../modules/php4

don't ask us why, ask the php guys. ;)

> -lmodphp4      -lm       -L/usr/local/lib  
> /usr/local/lib/perl5/5.8.3/darwin-2level/auto/DynaLoader/DynaLoader.a  
> -L/usr/local/lib/perl5/5.8.3/darwin-2level/CORE -lperl -ldl -lm -lc
> ld: warning -L: directory name (../modules/php4) does not exist
> ld: warning -L: directory name (../../modules/php4) does not exist

so these are just warnings, ignore them.

> ld: table of contents for archive: modules/php4/libmodphp4.a is out of  
> date; rerun ranlib(1) (can't load from it)

do you think that's the cause of the error? can you build mod_php4 on its own? 
I'd try to do that first, as the cause of the problem could be in the mod_php 
land.

> ld: warning prebinding disabled because dependent library:  
> /usr/lib/libdl.0.dylib is not prebound

i'm not a darwin user, so i'm not sure whether this is important, but as it 
says it's a warning, let's hope that it's harmless.

> make: *** [dummy] Error 1


>> 73,
>> Ged.
>
> what does 73 stand for?

good bye in morse:
http://www.envf.port.ac.uk/illustration/z/hig/71to80/73/jb/73.htm

__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html


Re: apache + mod_perl + mod_php fails

Posted by Stas Bekman <st...@stason.org>.
Ged Haywood wrote:
> Hi Stas,
> 
> On Thu, 18 Mar 2004, Stas Bekman wrote:
> 
> 
>>FWIW, EVERYTHING=1 has nothing to do with Apache.
> 
> 
> I was just looking at this in mod_perl-1.27/Makefile.PL:
> 
> if($EVERYTHING) {
>     @callback_hooks{qw(PERL_STACKED_HANDLERS PERL_METHOD_HANDLERS)} = (1) x 2;
>     for(qw(ALL_HOOKS PERL_SSI PERL_SECTIONS PERL_DIRECTIVE_HANDLERS
>            PERL_LOG_API PERL_URI_API PERL_UTIL_API PERL_TABLE_API PERL_FILE_API)) {
>        $$_ = 1;
>     }
> }
> 
> and it looked like there might be something there.
> 
> Apologies if it's a red herring.

No, problem, Ged.

That error clearly is a mod_php problem. look:

gcc  -DDARWIN -DMOD_PERL -DUSE_PERL_SSI -pipe -fno-common  -DPERL_DARWIN 
-no-cpp-precomp -fno-strict-aliasing -DUSE_EXPAT  -I./lib/expat-lite `./apaci` 
-I.  -I/usr/local/lib/perl5/5.8.3/darwin-2level/CORE    -o helpers/dummy 
helpers/dummy.c   -Lmodules/php4 -L../modules/php4 -L../../modules/php4 
-lmodphp4      -lm       -L/usr/local/lib 
/usr/local/lib/perl5/5.8.3/darwin-2level/auto/DynaLoader/DynaLoader.a 
-L/usr/local/lib/perl5/5.8.3/darwin-2level/CORE -lperl -ldl -lm -lc

it tries to link -lmodphp4 which has dynamic symbols from httpd and httpd is 
not part of that linking. that's why Michael gets this problem. I bet Michael 
will have the same problem with building mod_php on its own.

__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html


Re: apache + mod_perl + mod_php fails

Posted by Ged Haywood <ge...@jubileegroup.co.uk>.
Hi Stas,

On Thu, 18 Mar 2004, Stas Bekman wrote:

> FWIW, EVERYTHING=1 has nothing to do with Apache.

I was just looking at this in mod_perl-1.27/Makefile.PL:

if($EVERYTHING) {
    @callback_hooks{qw(PERL_STACKED_HANDLERS PERL_METHOD_HANDLERS)} = (1) x 2;
    for(qw(ALL_HOOKS PERL_SSI PERL_SECTIONS PERL_DIRECTIVE_HANDLERS
           PERL_LOG_API PERL_URI_API PERL_UTIL_API PERL_TABLE_API PERL_FILE_API)) {
       $$_ = 1;
    }
}

and it looked like there might be something there.

Apologies if it's a red herring.

73,
Ged.


-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html


Re: apache + mod_perl + mod_php fails

Posted by Stas Bekman <st...@stason.org>.
Ged Haywood wrote:
> Hi there,
> 
> On Thu, 18 Mar 2004, Michael wrote:
> 
> 
>>_actions_module
>>_include_module
>>_log_config_module
> 
> 
> I think there's stuff in apache's src/modules/standard directory which
> isn't being compiled.  You could check if/why things in there aren't
> built, or maybe wipe the directory trees and try again without the
> 
> EVERYTHING=1
> 
> directive.

FWIW, EVERYTHING=1 has nothing to do with Apache.

__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html


Re: apache + mod_perl + mod_php fails

Posted by Ged Haywood <ge...@jubileegroup.co.uk>.
Hi there,

On Thu, 18 Mar 2004, Michael wrote:

> _actions_module
> _include_module
> _log_config_module

I think there's stuff in apache's src/modules/standard directory which
isn't being compiled.  You could check if/why things in there aren't
built, or maybe wipe the directory trees and try again without the

EVERYTHING=1

directive.

> > what does 73 stand for?

>From the Morse code days, we used it to mean "best wishes".

--... ...--

Ged.

-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html


Re: apache + mod_perl + mod_php fails

Posted by Michael <mi...@gmx.net>.
OK, just saw myself that i should have run ranlib. after that and  
another configure and make i get:
ld: warning -L: directory name (../modules/php4) does not exist
ld: warning -L: directory name (../../modules/php4) does not exist
ld: warning prebinding disabled because dependent library:  
/usr/lib/libdl.0.dylib is not prebound
ld: Undefined symbols:
_actions_module
_include_module
_log_config_module
make[2]: *** [target_static] Error 1
make[1]: *** [build-std] Error 2
make: *** [build] Error 2



Am 18. Mär 2004 um 19:18 schrieb Michael:

> Hello Ged,
>
> I copied all files to my ~ and repeated all setps. After make in point  
> 4 i now get:
> <snip>
> ** A test compilation with your Makefile configuration
> ** failed.  The below error output from the compilation
> ** test will give you an idea what is failing. Note that
> ** Apache requires an ANSI C Compiler, such as gcc.
>
> ======== Error Output for sanity check ========
> cd ..; gcc  -DDARWIN -DMOD_PERL -DUSE_PERL_SSI -pipe -fno-common  
> -DPERL_DARWIN -no-cpp-precomp -fno-strict-aliasing -DUSE_EXPAT  
> -I./lib/expat-lite `./apaci` -I.  
> -I/usr/local/lib/perl5/5.8.3/darwin-2level/CORE    -o helpers/dummy  
> helpers/dummy.c   -Lmodules/php4 -L../modules/php4  
> -L../../modules/php4 -lmodphp4      -lm       -L/usr/local/lib  
> /usr/local/lib/perl5/5.8.3/darwin-2level/auto/DynaLoader/DynaLoader.a  
> -L/usr/local/lib/perl5/5.8.3/darwin-2level/CORE -lperl -ldl -lm -lc
> ld: warning -L: directory name (../modules/php4) does not exist
> ld: warning -L: directory name (../../modules/php4) does not exist
> ld: table of contents for archive: modules/php4/libmodphp4.a is out of  
> date; rerun ranlib(1) (can't load from it)
> ld: warning prebinding disabled because dependent library:  
> /usr/lib/libdl.0.dylib is not prebound
> make: *** [dummy] Error 1
> ============= End of Error Report =============
>
>  Aborting!
> </snip>
>
> As advised i only did make install with sudo.
>
> Am 18. Mär 2004 um 18:10 schrieb Ged Haywood:
>
>> Hi there,
>>
>> On Thu, 18 Mar 2004, Michael wrote:
>>
>>> I have problems compiling apache under mac os x. I had no problems
>>> without php but with php it doesn't work. Furthermore i need
>>> mod_rewrite. I consulted docs at perl.apache.org and the  
>>> install-guide
>>> in practical mod_perl. What i did starting in /usr/local/src:
>>
>> Don't build things in /usr/local/src.  Build in your home directory,
>> as an unprivileged user, only do 'make install' as root.  Otherwise
>> you will probably run into a few permissions problems.  That might be
>> the cause of your problem here but I'd like to hear what happens when
>> you build in your home directory before claiming victory on this one.
>>
>> Stas, I notice that in
>>
>> http://perl.apache.org/docs/1.0/guide/ 
>> install.html#A_Summary_of_a_Basic_mod_perl_Installation
>>
>> we start with
>>
>> % cd /usr/src
>> % lwp-download ...
>>
>> which clearly won't work in the vast majority of installations because
>> a non-root user won't have write permission there.  I can't believe we
>> haven't noticed that before, it should be changed.  Shall I do it?
>>
>> 73,
>> Ged.
>
> what does 73 stand for?
>
>>
>> -- 
>> Report problems: http://perl.apache.org/bugs/
>> Mail list info: http://perl.apache.org/maillist/modperl.html
>> List etiquette: http://perl.apache.org/maillist/email-etiquette.html
>>
>
>
> --
> Report problems: http://perl.apache.org/bugs/
> Mail list info: http://perl.apache.org/maillist/modperl.html
> List etiquette: http://perl.apache.org/maillist/email-etiquette.html
>


-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html


Re: apache + mod_perl + mod_php fails

Posted by Michael <mi...@gmx.net>.
Hello Ged,

I copied all files to my ~ and repeated all setps. After make in point  
4 i now get:
<snip>
** A test compilation with your Makefile configuration
** failed.  The below error output from the compilation
** test will give you an idea what is failing. Note that
** Apache requires an ANSI C Compiler, such as gcc.

======== Error Output for sanity check ========
cd ..; gcc  -DDARWIN -DMOD_PERL -DUSE_PERL_SSI -pipe -fno-common  
-DPERL_DARWIN -no-cpp-precomp -fno-strict-aliasing -DUSE_EXPAT  
-I./lib/expat-lite `./apaci` -I.  
-I/usr/local/lib/perl5/5.8.3/darwin-2level/CORE    -o helpers/dummy  
helpers/dummy.c   -Lmodules/php4 -L../modules/php4 -L../../modules/php4  
-lmodphp4      -lm       -L/usr/local/lib  
/usr/local/lib/perl5/5.8.3/darwin-2level/auto/DynaLoader/DynaLoader.a  
-L/usr/local/lib/perl5/5.8.3/darwin-2level/CORE -lperl -ldl -lm -lc
ld: warning -L: directory name (../modules/php4) does not exist
ld: warning -L: directory name (../../modules/php4) does not exist
ld: table of contents for archive: modules/php4/libmodphp4.a is out of  
date; rerun ranlib(1) (can't load from it)
ld: warning prebinding disabled because dependent library:  
/usr/lib/libdl.0.dylib is not prebound
make: *** [dummy] Error 1
============= End of Error Report =============

  Aborting!
</snip>

As advised i only did make install with sudo.

Am 18. Mär 2004 um 18:10 schrieb Ged Haywood:

> Hi there,
>
> On Thu, 18 Mar 2004, Michael wrote:
>
>> I have problems compiling apache under mac os x. I had no problems
>> without php but with php it doesn't work. Furthermore i need
>> mod_rewrite. I consulted docs at perl.apache.org and the install-guide
>> in practical mod_perl. What i did starting in /usr/local/src:
>
> Don't build things in /usr/local/src.  Build in your home directory,
> as an unprivileged user, only do 'make install' as root.  Otherwise
> you will probably run into a few permissions problems.  That might be
> the cause of your problem here but I'd like to hear what happens when
> you build in your home directory before claiming victory on this one.
>
> Stas, I notice that in
>
> http://perl.apache.org/docs/1.0/guide/ 
> install.html#A_Summary_of_a_Basic_mod_perl_Installation
>
> we start with
>
> % cd /usr/src
> % lwp-download ...
>
> which clearly won't work in the vast majority of installations because
> a non-root user won't have write permission there.  I can't believe we
> haven't noticed that before, it should be changed.  Shall I do it?
>
> 73,
> Ged.

what does 73 stand for?

>
> -- 
> Report problems: http://perl.apache.org/bugs/
> Mail list info: http://perl.apache.org/maillist/modperl.html
> List etiquette: http://perl.apache.org/maillist/email-etiquette.html
>


-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html


Re: apache + mod_perl + mod_php fails

Posted by Stas Bekman <st...@stason.org>.
Ged Haywood wrote:
> Hi there,
> 
> On Thu, 18 Mar 2004, Michael wrote:
> 
> 
>>I have problems compiling apache under mac os x. I had no problems
>>without php but with php it doesn't work. Furthermore i need
>>mod_rewrite. I consulted docs at perl.apache.org and the install-guide
>>in practical mod_perl. What i did starting in /usr/local/src:
> 
> 
> Don't build things in /usr/local/src.  Build in your home directory,
> as an unprivileged user, only do 'make install' as root.  Otherwise
> you will probably run into a few permissions problems.  That might be
> the cause of your problem here but I'd like to hear what happens when
> you build in your home directory before claiming victory on this one.

Not really, Ged. Not with mp1.

> Stas, I notice that in
> 
> http://perl.apache.org/docs/1.0/guide/install.html#A_Summary_of_a_Basic_mod_perl_Installation
> 
> we start with
> 
> % cd /usr/src
> % lwp-download ...
> 
> which clearly won't work in the vast majority of installations because
> a non-root user won't have write permission there.  I can't believe we
> haven't noticed that before, it should be changed.  

We haven't noticed, simply because the problem does not exist.

> Shall I do it?

Please don't. This location is used all over the place and that change will 
just make things confusing. if you want to change you will need to read and 
change it in *many* other places all over that chapter and others as well. And 
s/// won't work, because in some places it must be /usr/src.

mod_perl 1 has no problems building and testing as root, so let's just keep it 
that way. better spend time on working on the mod_perl 2 docs, which need a 
lot of help. ;)

__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html


Re: apache + mod_perl + mod_php fails

Posted by "Ruslan U. Zakirov" <cu...@wr.miee.ru>.
Stas wrote:
SB> Ruslan U. Zakirov wrote:
>> Another thing about installation guide:
>> http://perl.apache.org/docs/1.0/guide/install.html#mod_perl_and_mod_php
>> 1) Configure Apache.
>> 
>>   % cd apache_1.3.xx
>>   % ./configure --prefix=/usr/local/etc/httpd
>> Why should I do this, I allways skip this step and everything fine. I
>> don't understand why I should configure Apache before modules if I use
>> APACI interface which primary advantage is ability to do it later.


SB> it's has been awhile since i've last done that, but that step was needed at 
SB> that time. perhaps things have changed in the last few years, so it's no 
SB> longer required. but since we always have users who try to build older 
SB> versions, let's keep it there, as there is no harm in it. may be adding a 
SB> comment that the 1st step may not be needed with the recent packages is due.
Heh. Ok. Understood. Note would be good. It's a little confusing.

>> http://perl.apache.org/docs/1.0/guide/install.html#toc_The_Flexible_Way
>>   $ cd mod_perl-1.xx
>>   $ perl Makefile.PL \
>>       APACHE_SRC=../apache_1.3.xx/src \
>>       NO_HTTPD=1 \
>>       USE_APACI=1 \
>>       PREP_HTTPD=1 \
>>       EVERYTHING=1 \
>>       [...]
>>   $ make
>>   $ make install
>>   $ cd ..
>> 
>>   This isn't flexible way. If I run 'make install' before apache build
>>   and mod_perl test it could overwrite current files. Am I
>>   wrong here? What to do if apache build will fail and I have to wait
>>   for fix?

SB> overwrite what files? previous mod_perl build?
Ugu.
SB> sure, don't run 'make install'
SB> then. you will have exactly the same problem with any other scenario where 
SB> each module needs to run its own 'make install'.
Nope. I've done some test. php4 guys are bad at this point. If you
don't run 'make install' then apache-1.3.xx/src/modules/php4 would be
empty :( So you must run it to build apache. it write in other system dirs :(
         Thanks. Ruslan.


SB> __________________________________________________________________
SB> Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
SB> http://stason.org/     mod_perl Guide ---> http://perl.apache.org
SB> mailto:stas@stason.org http://use.perl.org http://apacheweek.com
SB> http://modperlbook.org http://apache.org   http://ticketmaster.com




-- 
С уважением,
 Ruslan                          mailto:cubic@wr.miee.ru


-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html


Re: apache + mod_perl + mod_php fails

Posted by Stas Bekman <st...@stason.org>.
Ruslan U. Zakirov wrote:
> Another thing about installation guide:
> http://perl.apache.org/docs/1.0/guide/install.html#mod_perl_and_mod_php
> 1) Configure Apache.
> 
>   % cd apache_1.3.xx
>   % ./configure --prefix=/usr/local/etc/httpd
> Why should I do this, I allways skip this step and everything fine. I
> don't understand why I should configure Apache before modules if I use
> APACI interface which primary advantage is ability to do it later.


it's has been awhile since i've last done that, but that step was needed at 
that time. perhaps things have changed in the last few years, so it's no 
longer required. but since we always have users who try to build older 
versions, let's keep it there, as there is no harm in it. may be adding a 
comment that the 1st step may not be needed with the recent packages is due.

> http://perl.apache.org/docs/1.0/guide/install.html#toc_The_Flexible_Way
>   $ cd mod_perl-1.xx
>   $ perl Makefile.PL \
>       APACHE_SRC=../apache_1.3.xx/src \
>       NO_HTTPD=1 \
>       USE_APACI=1 \
>       PREP_HTTPD=1 \
>       EVERYTHING=1 \
>       [...]
>   $ make
>   $ make install
>   $ cd ..
> 
>   This isn't flexible way. If I run 'make install' before apache build
>   and mod_perl test it could overwrite current files. Am I
>   wrong here? What to do if apache build will fail and I have to wait
>   for fix?

overwrite what files? previous mod_perl build? sure, don't run 'make install' 
then. you will have exactly the same problem with any other scenario where 
each module needs to run its own 'make install'.


__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html


Re: apache + mod_perl + mod_php fails

Posted by "Ruslan U. Zakirov" <cu...@wr.miee.ru>.
Another thing about installation guide:
http://perl.apache.org/docs/1.0/guide/install.html#mod_perl_and_mod_php
1) Configure Apache.

  % cd apache_1.3.xx
  % ./configure --prefix=/usr/local/etc/httpd
Why should I do this, I allways skip this step and everything fine. I
don't understand why I should configure Apache before modules if I use
APACI interface which primary advantage is ability to do it later.

http://perl.apache.org/docs/1.0/guide/install.html#toc_The_Flexible_Way
  $ cd mod_perl-1.xx
  $ perl Makefile.PL \
      APACHE_SRC=../apache_1.3.xx/src \
      NO_HTTPD=1 \
      USE_APACI=1 \
      PREP_HTTPD=1 \
      EVERYTHING=1 \
      [...]
  $ make
  $ make install
  $ cd ..

  This isn't flexible way. If I run 'make install' before apache build
  and mod_perl test it could overwrite current files. Am I
  wrong here? What to do if apache build will fail and I have to wait
  for fix?
              Best regards. Ruslan.


GH> Hi there,

GH> On Thu, 18 Mar 2004, Michael wrote:

>> I have problems compiling apache under mac os x. I had no problems
>> without php but with php it doesn't work. Furthermore i need
>> mod_rewrite. I consulted docs at perl.apache.org and the install-guide
>> in practical mod_perl. What i did starting in /usr/local/src:

GH> Don't build things in /usr/local/src.  Build in your home directory,
GH> as an unprivileged user, only do 'make install' as root.  Otherwise
GH> you will probably run into a few permissions problems.  That might be
GH> the cause of your problem here but I'd like to hear what happens when
GH> you build in your home directory before claiming victory on this one.

GH> Stas, I notice that in

GH> http://perl.apache.org/docs/1.0/guide/install.html#A_Summary_of_a_Basic_mod_perl_Installation

GH> we start with

GH> % cd /usr/src
GH> % lwp-download ...

GH> which clearly won't work in the vast majority of installations because
GH> a non-root user won't have write permission there.  I can't believe we
GH> haven't noticed that before, it should be changed.  Shall I do it?

GH> 73,
GH> Ged.




-- 
С уважением,
 Ruslan                          mailto:cubic@wr.miee.ru


-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html


Re: apache + mod_perl + mod_php fails

Posted by Ged Haywood <ge...@jubileegroup.co.uk>.
Hi there,

On Thu, 18 Mar 2004, Michael wrote:

> I have problems compiling apache under mac os x. I had no problems
> without php but with php it doesn't work. Furthermore i need
> mod_rewrite. I consulted docs at perl.apache.org and the install-guide
> in practical mod_perl. What i did starting in /usr/local/src:

Don't build things in /usr/local/src.  Build in your home directory,
as an unprivileged user, only do 'make install' as root.  Otherwise
you will probably run into a few permissions problems.  That might be
the cause of your problem here but I'd like to hear what happens when
you build in your home directory before claiming victory on this one.

Stas, I notice that in

http://perl.apache.org/docs/1.0/guide/install.html#A_Summary_of_a_Basic_mod_perl_Installation

we start with

% cd /usr/src
% lwp-download ...

which clearly won't work in the vast majority of installations because
a non-root user won't have write permission there.  I can't believe we
haven't noticed that before, it should be changed.  Shall I do it?

73,
Ged.

-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html