From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:54900) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UcvXk-0005P0-3L for qemu-devel@nongnu.org; Thu, 16 May 2013 06:36:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UcvXh-0005NR-7B for qemu-devel@nongnu.org; Thu, 16 May 2013 06:36:16 -0400 Received: from mx1.redhat.com ([209.132.183.28]:46216) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UcvXg-0005NI-Vr for qemu-devel@nongnu.org; Thu, 16 May 2013 06:36:13 -0400 Message-ID: <5194B726.6050201@redhat.com> Date: Thu, 16 May 2013 12:38:30 +0200 From: Laszlo Ersek MIME-Version: 1.0 References: <1368225970-28506-1-git-send-email-mdroth@linux.vnet.ibm.com> <20130515091746.68ee3f4d@redhat.com> <20130515143237.GM13213@vm> <20130515110427.5b8b4fbf@redhat.com> <20130515174224.GN13213@vm> <20130515140558.7687e36f@redhat.com> <20130515191309.GB23880@vm> In-Reply-To: <20130515191309.GB23880@vm> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v3 00/11] qapi: add support for lists of native types List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: mdroth Cc: akong@redhat.com, qemu-devel@nongnu.org, Luiz Capitulino On 05/15/13 21:13, mdroth wrote: > On Wed, May 15, 2013 at 02:05:58PM -0400, Luiz Capitulino wrote: >> On Wed, 15 May 2013 12:42:24 -0500 >> mdroth wrote: >>> The only way I've managed to reproduce this is by having a stale >>> qapi-types.h hanging around in $SRC_DIR while i'm building in a >>> different $BUILD_DIR. Can you confirm that's not what's happening here? >> >> Yes, it was :( I had an old qapi-types.h in $SRC_DIR, but was building >> in a different $BUILD_DIR. I am really sorry for having wasted your time >> on this. >> >> I've applied this series to qmp-next branch, but I have no idea how I ended >> up with a qapi-types.h file in $SRC_DIR. I have an alias to build qemu that >> I use for several months now... >> > > No problem, only thought to check that scenario because it happens to me > all the time :) Side question: what's a common use case for a separate $BUILD_DIR? I just use "git clean -fdx" in $SRC_DIR instead of "make clean". The need to reconfigure (and to regenerate my tags file from scratch) is a small price to pay for the peace of mind. Thanks Laszlo