Hi, Thanks a ton! > If you want to refer to the path in C code as a macro "LOCALSTATEDIR", > you have in Makefile.am: > > AM_CPPFLAGS = -DLOCALSTATEDIR=\"$(pkglocalstatedir)\" But is pkglocalstatedir predefined, like pkgdatadir, pkglibdir, and pkgincludedir? It doesn't seem like it. If I just do the above, I wind up with LOCALSTATEDIR being '/'. Am I first supposed to do something like: pkglocalstatedir = $(localstatedir)/@PACKAGE@ If I do, that seems to work as intended. Regarding the GNU Coding Standards vs. FHS discrepancy in where the files wind up getting installed, am I safe to assume that as the "upstream guy" I can just follow the Autotools defaults? The distro packagers ought to know to use "./configure --localstatedir=/var" to get these files into the FHS-approved place, right? Thanks, David _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
