From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.4.2-2 i686)
because of the apache config file in /etc madness, when apxs adds the line
"LoadModule foo_module lib/apache/mod_foo.so" to httpd.conf, apache tries
to look for the modules relative to /conf's parent directory (in this case,
You've got a modules symlink, which unfortunately doesn't help, given
apxs's choice of paths.
The solution is quite simple. I made a symlink in /etc/httpd called 'lib'
that points to '/usr/lib'. The obvious alternative solution is to hack
apxs to use a path that fits with the modules symlink already in
Steps to Reproduce:
1. apxs -i -a apache_module.so
2. start apache
Actual Results: apache failed to load the module, as it couldn't find it.
Expected Results: apache should have found and loaded the module.
FYI, I just ran into the same problem, and I was glad to find this bug (now I
don't have to report it ;-). Kijiki0's fix worked for me as well:
ln -s /usr/lib /etc/httpd/lib
I suppose an errata apache-devel is in order, eh?
Thanks for the great software and hard work, Red Hat engineers!
Setting the execprefix to /usr while setting the prefix to /etc/httpd seems to
fix this weirdness with apxs. It'll be folded into a pending errata of 1.3.20
and into Raw Hide.
Confirmed fixed in apache-1.3.27-2. apxs now correctly adds the /usr prefix to
the LoadModule line.