I was going throught the steps and go to suPHP, in particular: cd /tmp wget http://suphp.org/download/suphp-0.7.1.tar.gz tar xvfz suphp-0.7.1.tar.gz cd suphp-0.7.1/ ./configure --prefix=/usr --sysconfdir=/etc --with-apr=/usr/bin/apr-1-config --with-apxs=/usr/sbin/apxs --with-apache-user=apache --with-setid-mode=owner --with-php=/usr/bin/php-cgi --with-logfile=/var/log/httpd/suphp_log --enable-SUPHP_USE_USERGROUP=yes make make install However, when processing the .configure I received the following: checking for APR... yes checking for dynamic Apache module support (via APXS)... cannot open /httpd/build/config_vars.mk: No such file or directory at /usr/sbin/apxs line 201. cannot open /httpd/build/config_vars.mk: No such file or directory at /usr/sbin/apxs line 201. ./configure: line 20370: /: is a directory cannot open /httpd/build/config_vars.mk: No such file or directory at /usr/sbin/apxs line 201. cannot open /httpd/build/config_vars.mk: No such file or directory at /usr/sbin/apxs line 201. cannot open /httpd/build/config_vars.mk: No such file or directory at /usr/sbin/apxs line 201. found at /usr/sbin/apxs (version ) checking for set-UID/set-GID mode... ok - using owner configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating src/apache/Makefile config.status: creating src/apache2/Makefile config.status: creating src/config.h config.status: src/config.h is unchanged config.status: executing depfiles commands So I searched for the files in question and was returned the following: [root@jpdsys1 suphp-0.7.1]# cd $HOME [root@jpdsys1 ~]# find / -name apxs /usr/sbin/apxs [root@jpdsys1 ~]# find / -name config_vars.mk /usr/lib64/httpd/build/config_vars.mk /usr/lib/httpd/build/config_vars.mk So, it appears all of the required files are on the machine, but what needs to be done to correct this error? Gene
Yes sir. I just entered: system-config-securitylevel And SELinux shows as disabled. Since this is a build I can re-do, I searched and found suphp in rpm form. I installed it and copied the module from the rpm's default location to the location your process was expecting and I was able to start HTTPD without error. But, I am sure that this will not work in the long run. Gene
This seems to be related to a bug in yum for CentOS. See http://bugs.centos.org/view.php?id=2934 I re-installed apr-devel and httpd-devel, and it worked.
