Build method options for dynamic modules
There are two common methods we can use to build dynamic modules: Apache extension tool (apxs) and module-provided configuration scripts.
The two common options for building dynamic modules are:
- Apache extension tool (apxs). IBM HTTP Server provides the apxs tool for building dynamic modules. We can build and install most modules with apxs. Here is an example:
# /usr/IBM IHS/bin/apxs -ci mod_example.cTo use the apxs tool, verify that Perl V5.003 or later is installed and that the path to the Perl executable on the first line of apxs is correct. See Apache APXS for more information.
- Module-provided configuration scripts. Some complex modules cannot be built directly with apxs, and instead provide their own configuration scripts for building the module. Consult the documentation provided with the module for detailed instructions. Check for special configuration options that must point to the IBM HTTP Server installation directory, or the apxs program installed with IBM HTTP Server.
The configuration scripts for some modules check specifically for the use of Apache HTTP Server and will not work properly with IBM HTTP Server. In that case, install Apache V2.0.47 and build the module for Apache V2.0.47, then use the resulting dynamic module (mod_example.so) with IBM HTTP Server.
IBM HTTP Server customers occasionally try to use third-party modules which do not build or run properly on their platform with either Apache HTTP Server or IBM HTTP Server. Whenever there are build or run-time concerns with third-party modules, first verify that it builds and operates properly with Apache HTTP Server on the same machine. If problems are encountered with Apache HTTP Server, the module cannot be expected to work with IBM HTTP Server.
Related tasks
Extending IBM HTTP Server functionality with third-party plug-in modules