From mboxrd@z Thu Jan 1 00:00:00 1970 From: Farkas Levente Subject: Re: [ kvm-Bugs-1807620 ] KVM's --disable-gcc-check doesn't work Date: Thu, 04 Oct 2007 21:49:00 +0200 Message-ID: <470543AC.50901@bppiac.hu> References: <470515DA.9080606@bppiac.hu> <1191516896.5019.83.camel@ghaskins-t60p.haskins.net> <47052269.80501@bppiac.hu> <1191519749.5019.99.camel@ghaskins-t60p.haskins.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel , Discussion about the virtualization on CentOS Return-path: In-Reply-To: <1191519749.5019.99.camel-5CR4LY5GPkvLDviKLk5550HKjMygAv58XqFh9Ls21Oc@public.gmane.org> 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 Gregory Haskins wrote: > On Thu, 2007-10-04 at 19:27 +0200, Farkas Levente wrote: > >> ok but now as qemu code was imported into kvm, then it's probably would >> be better to witch gcc-4.x? > > Sure. Are you volunteering? ;) I'm sure both upstream QEMU developers, > KVM developers, and the community using either would be most > appreciative. I know I would be. here i mean that packaging kvm for fedora/redhat/centos using gcc-4.x in stead of gcc-3.x. if currently there is no reason to use gcc-3.x than i change all of my spec file. ps. anyway it's planed to be temporary or permanent to use a qemu fork for kvm and not try to propagate changes back to the upstream qemu? -- Levente "Si vis pacem para bellum!" ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/