From: Christoph Egger <chegger@amazon.de>
To: xen-devel <xen-devel@lists.xen.org>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: [PATCH] Make sure to use tools as found by configure
Date: Fri, 10 May 2013 13:59:53 +0200 [thread overview]
Message-ID: <518CE139.6080701@amazon.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1786 bytes --]
Hi,
attached patch makes the build process work as described at
http://wiki.xen.org/wiki/Compiling_Xen_From_Source_on_NetBSD
Without this patch compiling the xen kernel fails with
python: No such file or directory
Note, this patch enforces to run configure before you
can compile the xen kernel.
This is already required to build tools and stubdom anyway.
This makes an other patch work as submitted:
http://lists.xen.org/archives/html/xen-devel/2013-04/msg02098.html
Christoph
commit 7172e6e0020328d14638a0bbb66a52c905cb4b0b
Author: Christoph Egger <chegger@amazon.de>
Date: Thu Feb 7 14:29:19 2013 +0000
Make sure to use tools as found by configure.
Fold inclusion of Tools.mk into toplevel Config.mk.
Signed-off-by: Christoph Egger <chegger@amazon.de>
Reviewed-by: Matthew Wilson <msw@amazon.com>
diff --git a/Config.mk b/Config.mk
index b1f12ec..149f55a 100644
--- a/Config.mk
+++ b/Config.mk
@@ -7,6 +7,7 @@ endif
# fallback for older make
realpath = $(wildcard $(foreach file,$(1),$(shell cd -P $(dir $(file))
&& echo "$$PWD/$(notdir $(file))")))
+-include $(XEN_ROOT)/config/Tools.mk
-include $(XEN_ROOT)/.config
# A debug build of Xen and tools?
@@ -76,7 +77,6 @@ EXTRA_INCLUDES += $(EXTRA_PREFIX)/include
EXTRA_LIB += $(EXTRA_PREFIX)/lib
endif
-PYTHON ?= python
PYTHON_PREFIX_ARG ?= --prefix="$(PREFIX)"
# The above requires that PREFIX contains *no spaces*. This variable is
here
# to permit the user to set PYTHON_PREFIX_ARG to '' to workaround this bug:
diff --git a/tools/Rules.mk b/tools/Rules.mk
index 3f03a31..7694a7f 100644
--- a/tools/Rules.mk
+++ b/tools/Rules.mk
@@ -3,7 +3,6 @@
# `all' is the default target
all:
--include $(XEN_ROOT)/config/Tools.mk
include $(XEN_ROOT)/Config.mk
export _INSTALL := $(INSTALL)
[-- Attachment #2: patch_usetools.diff --]
[-- Type: text/plain, Size: 1258 bytes --]
commit 7172e6e0020328d14638a0bbb66a52c905cb4b0b
Author: Christoph Egger <chegger@amazon.de>
Date: Thu Feb 7 14:29:19 2013 +0000
Make sure to use tools as found by configure.
Fold inclusion of Tools.mk into toplevel Config.mk.
Signed-off-by: Christoph Egger <chegger@amazon.de>
diff --git a/Config.mk b/Config.mk
index b1f12ec..149f55a 100644
--- a/Config.mk
+++ b/Config.mk
@@ -7,6 +7,7 @@ endif
# fallback for older make
realpath = $(wildcard $(foreach file,$(1),$(shell cd -P $(dir $(file)) && echo "$$PWD/$(notdir $(file))")))
+-include $(XEN_ROOT)/config/Tools.mk
-include $(XEN_ROOT)/.config
# A debug build of Xen and tools?
@@ -76,7 +77,6 @@ EXTRA_INCLUDES += $(EXTRA_PREFIX)/include
EXTRA_LIB += $(EXTRA_PREFIX)/lib
endif
-PYTHON ?= python
PYTHON_PREFIX_ARG ?= --prefix="$(PREFIX)"
# The above requires that PREFIX contains *no spaces*. This variable is here
# to permit the user to set PYTHON_PREFIX_ARG to '' to workaround this bug:
diff --git a/tools/Rules.mk b/tools/Rules.mk
index 3f03a31..7694a7f 100644
--- a/tools/Rules.mk
+++ b/tools/Rules.mk
@@ -3,7 +3,6 @@
# `all' is the default target
all:
--include $(XEN_ROOT)/config/Tools.mk
include $(XEN_ROOT)/Config.mk
export _INSTALL := $(INSTALL)
[-- Attachment #3: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2013-05-10 11:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 11:59 Christoph Egger [this message]
2013-05-10 12:14 ` [PATCH] Make sure to use tools as found by configure Ian Campbell
2013-05-10 12:49 ` Tim Deegan
2013-05-10 17:06 ` Matt Wilson
2013-05-10 17:10 ` Matt Wilson
2013-05-13 9:51 ` Ian Campbell
2013-05-13 10:59 ` Christoph Egger
2013-05-13 20:32 ` Matt Wilson
2013-05-14 8:44 ` Ian Campbell
2013-05-14 9:09 ` Christoph Egger
2013-05-16 8:30 ` Matt Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=518CE139.6080701@amazon.de \
--to=chegger@amazon.de \
--cc=Ian.Campbell@citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.