* Paul Eggert wrote on Wed, May 17, 2006 at 07:37:18PM CEST: > Ralf Wildenhues <[EMAIL PROTECTED]> writes: > > > The config.status "special magic" from this patch: > > http://lists.gnu.org/archive/html/autoconf-patches/2006-05/msg00041.html > > doesn't work if we don't also use a program with an absolute name. > > What's the bug with it? Sorry, I don't follow.
Oh, I forgot to explain. Sorry about that. cat >configure.ac <<EOF AC_INIT AC_PROG_MKDIR_P AC_CONFIG_FILES(sub/foo) AC_OUTPUT EOF echo "@MKDIR_P@" > sub/foo.in autoconf ./configure On GNU/Linux, sub/foo will contain: ../mkdir -p > > OK to apply this patch to fix both? > > I'd rather not use an absolute name in the normal case. It makes > 'make' output look really ugly. In the normal case, $(MKDIR_P) should > expand to "mkdir -p", not to "/usr/local/bin/mkdir -p" or whatever. Well, then you need a different method in the config.status code to detect whether you need to munge with $MKDIR_P for subdirectories, i.e., a different way to detect that MKDIR_P contains a path that is relative to the build tree. Cheers, Ralf
