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.
Hi! I have never built mod_jk, but here are some thoughts > When compiling on Mac OS X, I get the following irritating warning: > > In file included from mod_jk.c:89: > In file included from ../common/jk_global.h:29: > ../common/config.h:81:9: warning: 'PACKAGE_NAME' macro redefined > #define PACKAGE_NAME "mod_jk" > ^ 1. I think that the PACKAGE_NAME define is generated by the following macro in native/configure.ac: dnl package and version. dnl synchronization with common/jk_version.h ? AC_INIT([mod_jk], [1.2.41]) > /usr/include/apache2/ap_config_auto.h:213:9: note: previous definition > is here > #define PACKAGE_NAME "" > ^ 2. From the path and file name, I think that the above header file belongs to Apache HTTPD, not mod_jk. It is no wonder that it has a different PACKAGE_NAME. > There are 3 others like it for a few other #defines. I would like to > clean these up, but I can't just commit changes to common/config.h > because it's auto-generated. > > Can anyone shed some light on where I can modify what gets dumped into > common/config.h? I see some stuff in config.status, but that in turn > gets generated by configure. > > Any suggestions? Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
