From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:37322) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eekCk-0004HH-Bw for qemu-devel@nongnu.org; Thu, 25 Jan 2018 11:16:47 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eekCj-0007YI-Il for qemu-devel@nongnu.org; Thu, 25 Jan 2018 11:16:46 -0500 Received: from mail-ot0-x22c.google.com ([2607:f8b0:4003:c0f::22c]:35222) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eekCj-0007Xx-Dc for qemu-devel@nongnu.org; Thu, 25 Jan 2018 11:16:45 -0500 Received: by mail-ot0-x22c.google.com with SMTP id 53so7162756otj.2 for ; Thu, 25 Jan 2018 08:16:45 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <151274735709.11243.12332071284435970530.malonedeb@soybean.canonical.com> <151686682161.4861.8851702267220024380.malone@wampee.canonical.com> From: Peter Maydell Date: Thu, 25 Jan 2018 16:16:24 +0000 Message-ID: Content-Type: text/plain; charset="UTF-8" Subject: Re: [Qemu-devel] [Bug 1737194] Re: Windows NT 4.0 fails to boot from qcow2 installation List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Bug 1737194 <1737194@bugs.launchpad.net> Cc: QEMU Developers On 25 January 2018 at 15:58, John Arbuckle wrote: > I did try to build at commits 306ec6c3cece7004429c79c1ac93d49919f1f1cc > and e689f7c668cbd9d08f330e17c3dd3a059c9553d3. Both failed to build on my > Mac OS X system. Here is the error message I usually saw: > > LINK qemu-io > Undefined symbols for architecture x86_64: > "_use_rt_clock", referenced from: > _bdrv_acct_start in block.o > _bdrv_acct_done in block.o > Undefined symbols for architecture x86_64: > _qemu_clock_get_ns in qemu-timer.o > "_use_rt_clock", referenced from: > _bdrv_acct_start in block.o > _bdrv_acct_done in block.o > _qemu_clock_get_ns in qemu-timer.o If you configure with --disable-tools does it manage to build, or does it just go on to fail to link the main QEMU binary with the same error? (We've had some issues in the past I think where configure put libraries on the main binary link line but not on the tools link lines, so maybe worth a try...) thanks -- PMM