Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have an operational and compiled from source Apache installation with shared modules enabled.

I now want to use mod_proxy but at the time I built my Apache server I didn't know I would need this and I didn't specify --enable-mod_proxy=shared and --enable-mod_proxy_http=shared when I ran ./configure.

On this page it suggests that I can do:

$ ./configure --prefix=/path/to/install --enable-foo=shared
$ make install

Will this only build the module specified and install it to the --prefix path, or will it rebuild all of Apache and redeploy that too?

share|improve this question
Wow, people are still building things like this from source? What distro are you using? – Tom O'Connor Nov 7 '11 at 0:57
@TomO'Connor - CentOS 5/6 but our builds are somewhat customised for our particular environment. – Kev Nov 7 '11 at 1:05
@TomO'Connor Some even use FreeBSD. – Anthony Rutledge Jun 27 '15 at 16:59
up vote 3 down vote accepted

It seems that mod_proxy/mod_proxy_http compiles with apxs works just fine:

apxs -i -c mod_proxy.c proxy_util.c
apxs -i -c mod_proxy_http.c
share|improve this answer
+1 for APXS.... – Tom O'Connor Nov 7 '11 at 16:39
@TomO'Connor - thanks :), don't know why I didn't think of that in the first place. – Kev Nov 7 '11 at 16:48

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.