Jim Meyering wrote: > Consider consistency with automake-generated rules. > For example, I see these uses of $(MKDIR_P) in coreutils/lib/Makefile: > ... > I think anyone wanting to use some other MKDIR_P value > would be surprised (and report it as a bug) to have to > resort to rerunning configure or config.status
OK, go ahead and make the substitution. I can see that in rare, rare cases, since MKDIR_P is a command, people may want to use different versions of it. But for things like @LIBINTL@ and @LIBSOCKET@, it is still better to write them as @LIBINTL@, not $(LIBINTL), because if the corresponding autoconf macro was not run, it makes the error appear on all platforms. Otherwise it's too easy to write a Makefile.am that builds fine on glibc systems but not on Solaris or MacOS X. Bruno
