Hello Jacob, On 2017-04-11 17:04, Jacob Champion wrote: > To me, what you've described looks like a bug. > > I have no idea how easy or difficult it would be to remove the internal > config macros from our distributed headers -- it looks like we've been > doing this for a *long* time. And if it's not easy to do without risking > compatibility, I would guess that we wouldn't attempt a fix for 2.4.x. > > See also https://bz.apache.org/bugzilla/show_bug.cgi?id=46578 , though I > don't necessarily agree with the proposed solution there.
Thanks for the info. Well, you don't necessarily have to remove them, but they have to be guarded somehow. e.g. pass a define ICOMPILEAPACHE to the build process and only then the generated file is used. This define must not show up in any compile options or apr/apu-config output. This is one way to fix this. Another one would be to split the file into a publc and private part and not distribute the private one. I will have a look at the link you provided. The current situation makes it impossible to use the autotools AC_CONFIG_HEADERS macro in a project that involves Apache httpd. (or at least when you require that include) Cheers, K. C. -- regards Helmut K. C. Tessarek lookup http://pool.sks-keyservers.net for KeyID 0xC11F128D /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */
