Why do I need mod_perl and mod_phop as static modules ? because there are some modules that required as it. For example for mod_perl, I need the HTML-Mason and at a paragraph in the readme file says:
"Using Mason with a mod_perl DSO may cause your Apache server to crash silently at startup, or fail intermittently. The fix for this problem is to install Apache/mod_perl with mod_perl compiled statically into the Apache binary. Packages of Apache with a static mod_perl are available around the net." and there are another modules with this requirement so, I write this, because, I found a solution to my problem. And there is how I solved it: #ebuild /path/of/mod_php.ebuild fetch #ebuild /path/of/mod_perl.ebuild fetch #ebuild /path/of/apache-1.3.33.ebuild fetch #ebuild /path/of/mod_php.ebuild unpack #ebuild /path/of/mod_perl.ebuild unpack #ebuild /path/of/apache-1.3.33.ebuild unpack Configure and compile, of course mod_php and mod_perl as static modules for apache (read the install of mod_perl and mod_php) #touch .configure for each work directoy (mod_php, mod_perl and apache) in order to tell portage that mod_php,mod_perl and apache are compiled #ebuild apache install #ebuild apache qmerge and ready. Thanks and .... I like Gentoo El mi�, 30-03-2005 a las 11:58 -0500, A. Khattri escribi�: > On Tue, 29 Mar 2005, MOLINA BRAVO FELIPE DE JESUS wrote: > > > But with this form the modules are installed as dinamic ... and static ... > > how??? > > Why do you need static modules? There's no difference in functionality > when using dynamic modules. I would be loathe to make mod_perl static - it > makes the Apache binary much much bigger. > > -- [email protected] mailing list
