gcc will complain about this. In gcc 4.0 and above you can turn this
off explicitly with -Wno-variadic-macros. In a future API it would be
nice to eliminate these macros.
-
-Debian rationale for not having upstream build packages (.deb files)
---------------------------------------------------------------------
-
-For debian, it is highly undesirable if the upstream source contains a
-debian directory as this one will never be the same as the "official"
-Debian one, and patching is easier if it's not around.
-
-Sometimes upstream insists on having the possibility to build Debian
-packages themselves, in which case it is best to have a debian
-directory in the CVS, but not ship it when doing "make dist".
-
-Sometimes upstream insists on shipping the debian directory to their
-users so these can easily build a .deb, which is really bad because
-they usually don't remember to change the Debian changelog and version
-accordingly, and generally don't know enough about Debian policy to
-make conforming packages.
-
-So in the end you will have different broken packages compiled on
-various systems floating around which all have the same version number
-and look like official packages.
-
- -- Robert Lemmen, 2006
-
-The same holds for .rpm packages. The Check maintainer for Fedora
-Extras, Tom 'spot' Callaway, confirmed that they do not depend on an
-upstream rpm target in Check.