So Miguel objects to any use of third-party m4 macros at all? Because these are the possibilities: 1. You install from your package manager 2. You install fro

So Miguel objects to any use of third-party m4 macros at all? Because these are the possibilities: 1. You install from your package manager 2. You install from a source tarball, which contains a configure script 3. You install the bleeding edge version from a development repository 4. You do 3. but somehow you managed to break your autotools install (and I don't really want to know how you did), or you're running a long-eoled distro that ships an ancient version of pkg-config that doesn't include the pkg.m4 macro. The fourth scenario can cause macro trouble, but it takes a sophisticated kind of user to install from development repositories rather than a better-supported option (not to mention breaking autotools), so I think it's on those users to troubleshoot and fetch the missing macro.