Am 07.01.2015 um 15:05 schrieb Christopher Schultz:
On 1/7/15 6:24 AM, Rainer Jung wrote:
Am 07.01.2015 um 03:15 schrieb Konstantin Kolinko:
2015-01-07 2:25 GMT+03:00 Christopher Schultz
<ch...@christopherschultz.net>:
All,
I give up. I can't seem to figure out exactly how common/config.h comes
into existence during the "configure" process.
It is created from common/config.h.in. Whereas most of the .in-based
files are created by configure (see configure.ac) in
AC_OUTPUT([
Makefile
apache-1.3/Makefile
apache-1.3/Makefile.apxs
apache-2.0/Makefile
apache-2.0/Makefile.apxs
common/Makefile
common/list.mk
common/jk_types.h
])
the config.h is handled by
AC_CONFIG_HEADER(common/config.h)
and the PACKAGE variable values come from
AC_INIT([mod_jk], [1.2.41])
Okay, but how can we tweak what comes out into common/config.h?
I don't really know, but I expect no easy way to fine-tune the file. It
is meant to be generated by autoconf and contain the configure detection
results in the form of defines.
So I applied a workaround in r1650036, that can be found in other
modules as well, namely undefining those vars before including our own
config.h.
That's exactly what I was going to do... just in config.h.
Which IMHO is harder or impossible to do.
Thanks for the heads up. I found it annoying as well and simply needed a
kick to look for a solution.
:)
I was going to take a look at all our native components to see if I
could get rid of all warnings on both Linux and Mac OS X (environments
to which I have easy access).
It looks like mod_jk builds on Mac OS X now with no warnings or anything
when using "-Wall -pedantic". Yay!
Great, thanks for checking.
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
