From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: buildbot failure in kvm on next-i386 Date: Wed, 18 Jul 2012 18:45:17 +0300 Message-ID: <5006DA0D.6000406@redhat.com> References: <20120718050528.4245140A98@buildbot.b1-systems.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: gollub@b1-systems.de, kvm@vger.kernel.org To: kvm@buildbot.b1-systems.de Return-path: Received: from mx1.redhat.com ([209.132.183.28]:8972 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754077Ab2GRPpY (ORCPT ); Wed, 18 Jul 2012 11:45:24 -0400 In-Reply-To: <20120718050528.4245140A98@buildbot.b1-systems.de> Sender: kvm-owner@vger.kernel.org List-ID: On 07/18/2012 08:05 AM, kvm@buildbot.b1-systems.de wrote: > The Buildbot has detected a new failure on builder next-i386 while building kvm. > Full details are available at: > http://buildbot.b1-systems.de/kvm/builders/next-i386/builds/590 > It seems like the config does not include CONFIG_KVM_GUEST. While it luckily caught this build bug, I'd like to have it enabled in the future to trap more kvm code build failures. -- error compiling committee.c: too many arguments to function