All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: James Jacobsson <slowcoder-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Patch to allow KVM to build without gcc 3.x
Date: Tue, 19 Dec 2006 12:14:41 +0200	[thread overview]
Message-ID: <4587BB91.4060704@qumranet.com> (raw)
In-Reply-To: <fe247b50612181122scd1b87bk79b6f4c6e3f49cf7-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

James Jacobsson wrote:
> Attached is a patch to allow KVM to build without gcc 3.x (by skipping
> building QEmu).
>
> The only changes are to the top-level configure script and Makefile.
>
> To build without QEmu, there is a new argument to configure, --no-qemu
>
> This patch applies to KVM release 7.
>


How about a "--build=kernel,libkvm,qemu" option, where you can omit the 
packages you don't want.

--build would default to all packages, or "libkvm,qemu" if 
--with-patched-kernel is given.

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

      parent reply	other threads:[~2006-12-19 10:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-18 19:22 Patch to allow KVM to build without gcc 3.x James Jacobsson
     [not found] ` <fe247b50612181122scd1b87bk79b6f4c6e3f49cf7-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2006-12-19 10:14   ` Avi Kivity [this message]

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=4587BB91.4060704@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=slowcoder-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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.