From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43558) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XOclD-00041k-GJ for qemu-devel@nongnu.org; Mon, 01 Sep 2014 21:19:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XOcl7-0005Ns-6O for qemu-devel@nongnu.org; Mon, 01 Sep 2014 21:19:51 -0400 Received: from mx1.redhat.com ([209.132.183.28]:22545) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XOcl6-0005Nm-VL for qemu-devel@nongnu.org; Mon, 01 Sep 2014 21:19:45 -0400 Date: Tue, 2 Sep 2014 09:19:39 +0800 From: Fam Zheng Message-ID: <20140902011939.GA5993@T430.redhat.com> References: <1409567710-26217-1-git-send-email-famz@redhat.com> <5404584D.9000702@redhat.com> <540460C1.6090806@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [PATCH v2] rules.mak: Fix DSO build by pulling in archive symbols List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini , Peter Maydell Cc: QEMU Developers On Mon, 09/01 13:07, Peter Maydell wrote: > On 1 September 2014 13:04, Paolo Bonzini wrote: > > Il 01/09/2014 13:46, Peter Maydell ha scritto: > >> So we could fix this by not compiling empty files... > > > > Easy for int128, even easier for getauxval (it's not a fastpath, so we > > can move the "always return 0" version from include/qemu/osdep.h to > > util/getauxval.c). > > > > I'm not sure how to detect that there generated-tracers.c is empty. > > Stefan, is it used by anything except $(CONFIG_TRACE_SIMPLE)? > > You could always put in a dummy function that isn't actually > used by anything. > > >> ranlib doesn't like that either (this one's a warning we've had for > >> a long time): > > > > Given this, do you consider th a blocker for this patch? > > The ranlib warnings are comparatively clear and only happen > when we link the .a file; the warnings we get out of nm are > rather uglier and more confusing and produced at every final > binary link. I'd certainly prefer it if we could fix them, but I > guess I won't absolutely insist on it. > Thanks both of you for tracking down the problem. Let's add 2>/dev/null to suppress the warning. Fam