Building Apache 2.4.29 from source and getting configtest errors

[l***@gmail.com]

I'm running Ubuntu Trusty and attempting to build Apache 2.4.29 from source. Everything seems to work just fine, but `apachectl start` complains that 'Include must have an absolute path, mods-enabled/*.load'. With the packaged versions of apache, wildcards in <Include> and <IncludeOptional> directives work just fine. I thought that I may be hitting a dependency issue, so I downloaded the latest apr and apr-util sources to compile and install. The same error appears. I have check the docs at apache.org and researched for the last couple of days but to no avail. Does anyone have any suggestions as to a solution?

[l***@gmail.com]

Steps I have taken:
1. Built apache with the packaged versions of apr and apr-util
2. Place apr and apr-util source tree in srclib and re-built apache with 'with-included-apr'
3. Built apr and apr-util separately, installed them, and then build apache against the newly installed packages.

No matter which approach I take, apache cannot handle the wildcards in the config file. Seems like I am missing a dependency somewhere, but I cannot figure out what it could be.

[l***@gmail.com]

What I have tried so far:

1. Built apache using the distro's version of apr and apr-util
2. Built apache using 'with-included-apr' and made sure apr and apr-util source trees were installed in srclib.
3. Built and installed apr and apr-util separately then built apache against the newly installed version of apr and apr-util.

No matter what I try, apache cannot handle wildcards in the config file. I have done nothing to the main config file other than copy it from Debian. I believe I am missing a dependency, but I cannot figure out which one. Based on apache's website, this should be a fairly simple build process.

[I R A Darth Aggie]

On Sat, 23 Dec 2017 16:21:35 -0800 (PST),

Post by l***@gmail.com
I'm running Ubuntu Trusty and attempting to build Apache 2.4.29 from source.

Why? what is wrong with the pre-built apache dpkgs?

[l***@gmail.com]

Post by I R A Darth Aggie
Why? what is wrong with the pre-built apache dpkgs?

I want to and why not? Someone else compiles them for packaging, I should be able to compile them on my own, right? One of the best ways to learn how things work.

[I R A Darth Aggie]

On Mon, 25 Dec 2017 06:35:27 -0800 (PST),

Post by l***@gmail.com

Post by I R A Darth Aggie
Why? what is wrong with the pre-built apache dpkgs?

I want to and why not? Someone else compiles them for packaging, I
should be able to compile them on my own, right? One of the best
ways to learn how things work.

Well, ok. Good luck!

[l***@gmail.com]

I just re-read my reply, and it sounded a bit snarky. I apologize for that. To provide a bit more context, I am experimenting with setting up vagrant boxes for development work, and I got interested in compiling apache and php from scratch in order to be a bit more selective on the enabled options. I have a bit of experience compiling software, so I didn't think it would be such a big deal.Apache does not list a ton of requirements, and I can get past the 'make' and 'make install', but for some reason, the new version is not parsing the config file correctly. I'm baffeled.