Topic: How do I compile Apache with all modules?

[tanquang]

I followed this guide to compile Apache: https://www.apachelounge.com/viewtopic.php?t=6462
Here is the command I use to compile:

[tangent]

That Apache build guide shows you need to pre-build and install a number of base support packages, including PCRE, OpenSSL, APR and APR-Util.

To persuade Apache to build the additional modules you mention, you'll need to pre-build and install a number of additional packages too.
Exactly what you need to pre-build varies from module to module, e.g. for mod_deflate you'll need zlib; for mod_lua you'll need lua; for mod_http2 you'll need nghttp2, etc.

Take a look in the Apache build cmake.log file, and you'll see what features it's currently found, e.g. (hopefully)

-- Summary of feature detection:
-- LIBXML2_FOUND ............ : TRUE
-- LUA51_FOUND .............. : TRUE
-- NGHTTP2_FOUND ............ : TRUE
-- OPENSSL_FOUND ............ : TRUE
-- ZLIB_FOUND ............... : TRUE
-- BROTLI_FOUND ............. : TRUE
-- CURL_FOUND ............... : TRUE
-- JANSSON_FOUND ............ : TRUE
-- APR_HAS_LDAP ............. : TRUE
-- APR_HAS_XLATE ............ : TRUE
-- APU_HAVE_CRYPTO .......... : TRUE

However, beware that some of these extra packages have their own dependencies (some optional), depending on the features you choose to build into them, e.g. nghttp2 is complex and requires zlib and openssl, but will make use of libev, libcares, libxml2, python, etc.

mod_fcgid is a separate package in its own right, and should be built after Apache; similarly with mod_security2.so should you choose to build it. For mod_fcgid (release 2.3.9), if you read the documentation, it comes with its own CMAKE build option, which will create mod_fcgid.so and drop it into the Apache modules folder. Hopefully this will help you get further with your missing modules, let the forum know how you get on.

[tanquang]

Hi, I compiled Expat, PCRE, OpenSSL, APR and APR-Util before compiling Apache.
The commands I use to compile depend a lot on the tutorial above. I omitted zlib during OpenSSL compilation because I got the

[tangent]

I would suggest you build zlib (1.2.11) first, since it has no other dependencies.

Using the same layout structure as per the Apache guide (https://www.apachelounge.com/viewtopic.php?t=6462), these are suitable build commands.

[tanquang]

So the compile order would be: expat, pcre, zlib, lua, OpenSSL (I can remove the no-zlib option at compile time), APR, APR-Util and finally Apache?
Then I don't change the command line when compiling Apache, I will get all the missing modules listed above. Right?
Are your OpenSSL compilation options the same as mine?

[tangent]

Based on the modules you list, the suggested build order would be zlib, pcre, expat, openssl, lua, apr, apr-util and httpd.

However, this still won't build all the modules you say are missing in your original post. As stated before, you'll need to build and install a number of additional packages first, before the missing modules will get built with httpd. You need to check the httpd build log details to find out what's needed.

If I run the httpd build with just the above packages, I get these warnings:

-- mod_brotli was requested but couldn't be built due to a missing prerequisite (BROTLI_FOUND)
-- mod_charset_lite was requested but couldn't be built due to a missing prerequisite (APR_HAS_XLATE)
-- mod_proxy_html was requested but couldn't be built due to a missing prerequisite (LIBXML2_FOUND)
-- mod_xml2enc was requested but couldn't be built due to a missing prerequisite (LIBXML2_FOUND)
-- mod_http2 was requested but couldn't be built due to a missing prerequisite (NGHTTP2_FOUND)
-- mod_md was requested but couldn't be built due to a missing prerequisite (CURL_FOUND)
-- mod_md was requested but couldn't be built due to a missing prerequisite (JANSSON_FOUND)
-- mod_proxy_http2 was requested but couldn't be built due to a missing prerequisite (NGHTTP2_FOUND)

So here you can see what packages are missing, e.g. brotli, libxml2, nghttp2, curl, jansson, and APR with XLATE which means you need apr-iconv.

If you look at the News and Hangout forum, you'll see the httpd 2.4.46 release page shows the dependencies used in that build, which basically matches all the packages you are missing.

So you can see, building a full Apache suite is not simple, nor for the feint hearted. Hence the need for gurus who run this site and build the packages for us!

Stick at it. Build the dependencies one by one, and iterate till you get there.

[tanquang]

How to compile apr-iconv using CMake? I don't see the cmake file in it's release source package.

[tangent]

Unfortunately, release 1.2.2 of apr-iconv doesn't support CMake. However, it does come with nmake files, apriconv.mak for static library build, and libapriconv.mak for dynamic library build.

Take a look at https://apr.apache.org and https://apr.apache.org/compiling_win32.html and read the documentation for details.

The build process is closely tied up with the APR build location, so you'll need to edit these make files to update the location of the various APR include files, depending on your chosen directory locations, e.g. using perl to edit the make files.

[tanquang]

Thank you very much. I wonder if the home page version is Relase or Debug or Release with Debug because their modules file size is different from the modules file size after I compile?
Also, could you help me with this topic: https://www.apachelounge.com/viewtopic.php?t=8482

[tangent]

I'm not sure if the Apache Lounge build is done with Release or RelWithDebInfo - you'd need to ask them.

Looking at your PHP topic, I believe James Blond has given you appropriate answers to your question. Building PHP versions from scratch, with a full set of matching extensions, is notoriously difficult, especially on Windows.

I'd download the pre-compiled binaries for the versions you want from https://windows.php.net/downloads/releases/archives, and then run PHP code through Apache using fcgid. Earlier in this topic I posted that you should build fcgid after httpd. It's quite straightforward and comes with support for CMake, e.g. for mod_fcgid-2.3.9

[tanquang]

Sadly PHP 5.3 and 5.4 have no x64 release, only x86 version. X86 versions won't work on Apache x64, that's why I need to find their x64 version.
But also thank you very much.

[admin]

Indeed @tangent. Apachelounge runs mod_fcgid only.

Thanks for jumping in.

[tanquang]

The latest Apache version (2.4.4 has had many changes that can no longer be compiled the old way. I got a few errors here: https://stackoverflow.com/questions/67944929/error-lnk2019-unresolved-external-symbol-referenced-when-compile-httpd
Can you review it?

[tangent]

Can I suggest you look at the following two topics, which outline an alternative method for compiling Apache and related support packages with CMake:

https://www.apachelounge.com/viewtopic.php?t=8609
https://www.apachelounge.com/viewtopic.php?t=8627

I've yet to update these topics for Apache 2.4.48, and the latest Openssl, Curl, etc. (I've been busy elsewhere of late), but the method and details are sound. Notably, you can compare the CMake options I've chosen to use, with those in your build process.

Specifically, with Curl, I build it twice; once with BUILD_SHARED_LIBS=ON and again with BUILD_SHARED_LIBS=OFF, since we need both static and dynamic libraries.

Also take a look at the discussion over Curl support for OpenSSL as well as Schannel. This also has a direct bearing on Apache module mod_md, as much as libcurl.lib

[tanquang]

You say cURL you will compile 2 times, the order is -DBUILD_SHARED_LIBS=ON first and -DBUILD_SHARED_LIBS=OFF is it correct?
Is this command line I wrote correct?

[tangent]

You need the first of these two options for CURL. Build, make, install; twice. If you look at the CMakeLists.txt file for CURL, it doesn't support building both static and dynamic in the one pass, viz:

[tanquang]

I got it. The problem I had on HTTPD 2.4.48 was that I had to specify libcurl in the CMakeLists.txt file, or else the same error occurred to me.