See this article for information on compiling Apache with compiled-in modules. We find that this works well in some cases. The big problem, though, is you have to be very careful that you don’t break your website at upgrade time. There are some options to httpd that help with this. The -l option will list the compiled-in modules, and the -v option will list the version. Do this on your compiled httpd before you install it:
[root@srv-4 bin]# ./httpd -l Compiled in modules: core.c mod_access.c mod_auth.c mod_include.c mod_log_config.c mod_setenvif.c prefork.c http_core.c mod_mime.c mod_autoindex.c mod_negotiation.c mod_dir.c mod_alias.c mod_so.c [root@srv-4 bin]# ./httpd -v Server version: Apache/2.0.54 Server built: Jul 28 2005 08:15:01 [root@srv-4 bin]# [root@srv-4 httpd-2.0.55]# ./httpd -l Compiled in modules: core.c mod_access.c mod_auth.c mod_include.c mod_log_config.c mod_setenvif.c prefork.c http_core.c mod_mime.c mod_autoindex.c mod_negotiation.c mod_dir.c mod_alias.c mod_so.c [root@srv-4 httpd-2.0.55]# ./httpd -v Server version: Apache/2.0.55 Server built: Nov 6 2005 19:25:44 [root@srv-4 httpd-2.0.55]# |
Do leave your previous source tree, as you should be able to reinstall quickly with make install if you make a mistake.
