Re: [suse-ppc] setting up PHP4 and Perl for apache 3.1.19
i guess my real issue is that I wish to use apache with php4 and perl, and I don't believe apache is setup on my system to this( i believe apache isn't compiled to use the mod_php4 and mod_perl modules.) upon typing: httpd -l I get: http_core.c mod_so.c but it doesn't list mod_php4, mod_perl, or any of the other modules I think I need. plus, my server pages don't seem to recognize php4 code in any way. can you tell what my issue is?
From: Christopher Mahmood
To: suse-ppc@suse.com Subject: Re: [suse-ppc] setting up PHP4 and Perl for apache 3.1.19 Date: Wed, 10 Apr 2002 11:39:02 -0700 * c G (susegoose@hotmail.com) [020410 08:41]:
my area of confusion is to whether or not the update rpms from ftp.suse.com apply themselves to the source code existant on my system that I installed as spms.
Source rpms are just archives or source code, patches, and spec file that tells rpm how to build a binary rpm from them. The update rpms will replace the binaries and libraries (e.g., /usr/sbin/httpd), the update source rpm will replace the stuff in /usr/src/packages/.
I want to ensure that the compilation and istall process for apache, php4, and perl all use source code that will produce files with the updates applied. (thus the need for updated source code)
I don't think I understand what you are trying to do. The installation docs for apache tell you how to build it from scratch which you don't need to do if you are using our rpms. If you want to build it from scratch for self-betterment or whatever the patches we have in our source rpm are against the pristine source so they will apply to the same version. This seems like a strange exercise though since the the apache-<version>.tar.gz in the source rpm is the identical to one you'll download from apache.org. Why just rpm --rebuild apache.spm and install the rpm you've built?
Also is there a method (syntax and all) that might be preferred to following the general "apache install (how-to)"?
You can see how we build it in the spec file. I don't know if that's to be preferred though.
--
-ckm
_________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp.
At 19:35 +0000 on 10/4/2002, c G wrote:
i guess my real issue is that I wish to use apache with php4 and perl, and I don't believe apache is setup on my system to this( i believe apache isn't compiled to use the mod_php4 and mod_perl modules.)
I'm not an expert on perl, but I am somewhat of an expert on PHP. Your apache has to be installed with the ability to have shared object modules, in order to use PHP. This option is likely to be compiled in an RPM as it makes it very easy to add any needed extensions separately. It doesn't need to have PHP linked to it in any particular way. And PHP can be compiled with the option --with-apxs to make it an apache module. Then you have to put the resulting so library in the appropriate directory under the apache tree. HTH Herouth -- EMAIL: herouth@spamcop.net HOME PAGE: http://herouth.port5.com/
* c G (susegoose@hotmail.com) [020410 12:36]:
i guess my real issue is that I wish to use apache with php4 and perl, and I don't believe apache is setup on my system to this( i believe apache isn't compiled to use the mod_php4 and mod_perl modules.)
upon typing: httpd -l
I get: http_core.c mod_so.c
but it doesn't list mod_php4, mod_perl, or any of the other modules I think I need.
plus, my server pages don't seem to recognize php4 code in any way. can you tell what my issue is?
Assuming you have the packages installed (check with rpm), what does /etc/rc.config.d/apache.rc.config contain? You should have something like: HTTPD_SEC_MOD_PERL=yes HTTPD_SEC_MOD_PHP=yes If those variables don't exist then you most likely don't have the packages installed. After correcting the file, recreate /etc/httpd/httpd.conf and assoc. files with /sbin/SuSEconfig and restart with rcapache restart -- -ckm
participants (3)
-
c G
-
Christopher Mahmood
-
Herouth Maoz