All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Egger <Christoph.Egger@amd.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: [PATCH] tools: use PREFIX when building upstream qemu
Date: Thu, 25 Oct 2012 12:38:43 +0200	[thread overview]
Message-ID: <508916B3.2030403@amd.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 350 bytes --]


use PREFIX when building upstream qemu.

Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>

-- 
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Einsteinring 24, 85689 Dornach b. Muenchen
Geschaeftsfuehrer: Alberto Bozzo
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632

[-- Attachment #2: xen_qemu_prefix.diff --]
[-- Type: text/plain, Size: 379 bytes --]

diff -r 3d327e56bff2 -r 6b73078a4403 tools/Makefile
--- a/tools/Makefile
+++ b/tools/Makefile
@@ -190,6 +190,7 @@ subdir-all-qemu-xen-dir: qemu-xen-dir-fi
 	fi; \
 	cd qemu-xen-dir; \
 	$$source/configure --enable-xen --target-list=i386-softmmu \
+		--prefix=$(PREFIX) \
 		--source-path=$$source \
 		--extra-cflags="-I$(XEN_ROOT)/tools/include \
 		-I$(XEN_ROOT)/tools/libxc \

[-- Attachment #3: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

             reply	other threads:[~2012-10-25 10:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-25 10:38 Christoph Egger [this message]
2012-10-25 12:39 ` [PATCH] tools: use PREFIX when building upstream qemu Ian Jackson
2012-10-26  9:47   ` Christoph Egger
2012-10-26 10:15     ` Ian Campbell
2012-10-26 11:09       ` Christoph Egger
2012-12-13 10:40   ` Ian Campbell
2012-12-13 14:22     ` Christoph Egger
2012-12-13 14:25       ` Ian Jackson
2012-12-13 14:41         ` Christoph Egger
2012-12-13 15:07           ` Ian Jackson
2013-01-10 21:50             ` Christoph Egger
2012-12-13 14:28       ` Ian Campbell

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=508916B3.2030403@amd.com \
    --to=christoph.egger@amd.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.