From: Horms Subject: [PATCH 11/11] build: Don't assume that mkbuildtree is executable Date: Mon, 10 Apr 2006 11:30:09 +0900 Message-ID: <20060410023009.15477.66080.sendpatchset@tabatha.lab.ultramonkey.org> References: <20060410022914.15477.13677.sendpatchset@tabatha.lab.ultramonkey.org> Return-path: In-Reply-To: <20060410022914.15477.13677.sendpatchset@tabatha.lab.ultramonkey.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com Cc: Magnus Damm , Horms List-Id: xen-devel@lists.xenproject.org # HG changeset patch # User Horms # Node ID f69f52013d13de62aa66bebfbab511ccebbfe222 # Parent 491d06219ffdc9e9b99a483fe948970b75d52e06 build: Don't assume that mkbuildtree is executable In some cases, say for instance for some bizzare reason the tree was checked out of CVS, which doens't neccessarily store file permissions, mkbuildtree may not be executable. I couldn't decide btween chmoding mkbuildtree, which changes the tree, and running sh mkbuildtree, which assumes its a shell script. I settled on the latter. Signed-Off-By: Horms diff -r 491d06219ffd -r f69f52013d13 buildconfigs/Rules.mk --- a/buildconfigs/Rules.mk Thu Mar 30 15:16:40 2006 +0900 +++ b/buildconfigs/Rules.mk Thu Mar 30 15:21:11 2006 +0900 @@ -121,14 +121,14 @@ linux-2.6-xen.patch: ref-linux-$(LINUX_V linux-2.6-xen.patch: ref-linux-$(LINUX_VER)/.valid-ref rm -rf tmp-$@ cp -al $( $@ || true rm -rf tmp-$@ %-xen.patch: ref-%/.valid-ref rm -rf tmp-$@ cp -al $( $@ || true rm -rf tmp-$@ diff -r 491d06219ffd -r f69f52013d13 buildconfigs/mk.linux-2.6-xen --- a/buildconfigs/mk.linux-2.6-xen Thu Mar 30 15:16:40 2006 +0900 +++ b/buildconfigs/mk.linux-2.6-xen Thu Mar 30 15:21:11 2006 +0900 @@ -23,8 +23,8 @@ build: $(LINUX_DIR)/include/linux/autoco rm -rf $(LINUX_DIR) cp -al $(