|
From: | Peter Johansson |
Subject: | problem with MKDIR_P defined as relative path to install-sh |
Date: | Thu, 28 Feb 2013 23:31:49 +1000 |
User-agent: | Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9.2.28) Gecko/20120306 Thunderbird/3.1.20 |
Hello, I have a make rule that essentially does test/foo/foo.tar.gz: cd test/foo && $(MKDIR_P) m4 && ...This has worked for long time since MKDIR_P is typically defined as 'mkdir -p'. However, tonight I got a bug report and the problem turned out to be that MKDIR_P was defined as 'build-aux/install-sh -c -d' which of course does not work after the 'cd'. I've switched order now so I first create directories and then cd down in desired directory. But would it make sense to defined MKDIR_P with absolute path instead, i.e., '$(abs_top_srcdir)/build-aux/install-sh -c -d' just to avoid these kind of problems that difficult to find as mkdir -p is typically available on machines on which I develop.
Cheers, Peter
[Prev in Thread] | Current Thread | [Next in Thread] |