From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH] Allow for Cross compile of user tools Date: Tue, 02 Oct 2007 07:59:00 +0200 Message-ID: <4701DE24.4030109@qumranet.com> References: <1191264989.18461.12.camel@laptop> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel To: jyoung5-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org Return-path: In-Reply-To: <1191264989.18461.12.camel@laptop> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org Jerone Young wrote: > This is the first of many patches to begin to make kvm source a lot > better for compiling for other architecture support (that is not x86 or > x86-64). > > This patch makes it possible so that someone on an x86 machine can cross > compile for an x86-64 machine and vice versa. So now you will have > config-$(arch).mak for each architecture, with specific architecture > rules. > > An example of this is for compiling x86-64 on an x86 machine is: > make KERNELDIR=~/tmp/kvm ARCH=x86_64 > This should be done via ./configure (I dislike ?= intensely). > This allows for someone with an x86 machine to compile for x86_64. Later > patches that I will be submitting will be for ppc and will make a few > more changes. > > What I would like though is comments on how everyone feels about this > approach. We are need of something like this to start ading ppc related > code. > > No problem for user/. I'd like to see this accepted by qemu-devel as well. -- Any sufficiently difficult bug is indistinguishable from a feature. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/