Re: PACKAGE, VERSION, & PACKAGE_VERSION

On Fri, Aug 7, 2009 at 4:33 PM, Bruno Haible wrote: >> why do I get a warning for them (but not for PACKAGE_*)? > Because redefinitions of C macros warrant maintainer attention. yes, but why am I not getting the warnings about PACKAGE_*? -- Sam Steingold

Re: PACKAGE, VERSION, & PACKAGE_VERSION

Sam Steingold wrote: > I now do get the warning: > > In file included from wildcard.c:4: > config.h:72:1: warning: "PACKAGE" redefined > In file included from wildcard.c:1: > /home/ssteingold/src/clisp/current/build-g-dynmod/linkkit/clisp.h:164:1: > warning: this is the location of the previous d

PACKAGE, VERSION, & PACKAGE_VERSION

Hi, I have the following setup: main package (with its own configure.in[1]) which imports stuff from gnulib ~20 sub-packages (each with its own configure.in[2]) of which 3 import stuff from gnulib. sub-packages include the main package's config.h before their own config.h. Every single config.h