Originally Posted by Teleute
Looking at the output from above just shows me the modules (which are the same, but the modules alone don't determine the libraries). Here's the info I've been working from, from the Apache 2.2 docs:
Sets the type of database file that is used to store the passwords. The default database type is determined at compile time. The availability of other types of database files also depends on compile-time settings.
It is crucial that whatever program you use to create your password files is configured to use the same type of database."
So this is one example of info I'm trying to find that doesn't seem to be shown in -V, but is still something set at compile time only. If this one exists, then I'm also concerned there might be others.
I hope this helps clarify a bit. :-) Thanks!
The output that was requested was the output of the diff
command. In general principle, if the situation is so simple that no additional details are needed, beyond what you've provided, then it would seem that the apache installations are so identical, except for the compile options about which you are concerned, that the diff likely shouldn't be showing a list of modules at all.
You posted the link to a portion of the apache configuration info. originally. I'm aware of it. What I'm not aware of are the exact details of your two apache installations, what interpretation you might be placing on the world "default" from the documentation, and exactly how you are going about building apache.
We can think in terms of the "default" type of authentication used by apache, the "default" sort of authentication provided by a directive that has a "default" specific to the directive, etc. I've gotten the impression that you might be placing some interpretation on the use of word "default" in the apache documentation, other then the one that would normally apply to the situation.
Notice from the documentation that "default" is an argument to the directive:
so rather than specifying a specific type of database:
using the "default" type of database can be specified:
You seem to be focusing on manual
compile options. Whereas I would normally think in terms of configuring the build environment for apache by other means.
If you won't provide the requested output of the diff, perhaps you could go to the directory where you placed the apache source code, and look at the output of a command sequence such as this:
./configure --help | less
and pay particular attention to the options matching patterns such as *mod*, and *auth*. It might give you some idea of how optional components of an apache build might typically be handled.