From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49598) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aa7aW-0000Qy-7S for qemu-devel@nongnu.org; Sun, 28 Feb 2016 15:05:09 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aa7aS-0002aR-Vw for qemu-devel@nongnu.org; Sun, 28 Feb 2016 15:05:08 -0500 Received: from mail-wm0-x232.google.com ([2a00:1450:400c:c09::232]:38017) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aa7aS-0002Z6-Pn for qemu-devel@nongnu.org; Sun, 28 Feb 2016 15:05:04 -0500 Received: by mail-wm0-x232.google.com with SMTP id l68so34378500wml.1 for ; Sun, 28 Feb 2016 12:05:04 -0800 (PST) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-ID: <20160228200501.4792399.20857.198@gmail.com> Date: Sun, 28 Feb 2016 22:05:01 +0200 From: XJDHDR In-Reply-To: References: <56C991DF.1040305@gmail.com> Subject: Re: [Qemu-devel] Can't compile QEMU 2.5.0 on Arch Linux ARM List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: QEMU Developers >> {standard input}:9097: Error: bad instruction `lock' >> {standard input}:9097: Error: bad instruction `addl $0,0(%rsp)' >> {standard input}:9412: Error: bad instruction `lock' >> {standard input}:9412: Error: bad instruction `addl $0,0(%rsp)' >> /home/share/qemu-devel/QEMU/src/qemu-2.5.0/rules.mak:57: recipe for targ= et >> 'hw/display/qxl.o' failed >> make: *** [hw/display/qxl.o] Error 1 >> =3D=3D> ERROR: A failure occurred in build(). >> Aborting... >This should really not happen because it implies that we >somehow ended up with x86 inline assembly. >Some things to test: >(1) if you configure QEMU with --disable-spice, does it build >OK, or does it just fail later on on some other source file?=E2=80=8E Thank you =E2=80=8Efor the assistance Peter I have managed to try your suggestion and made some progress. After I added= "--disable-spice", the code compiled without any error. This implies that = Spice was causing my problem. While this may indicate a problem with the spice portion of QEMU's code, I = am more convinced that I didn't compile Spice properly and that this is wha= t is causing me problems. I might test this or I might simply not bother wi= th Spice. Kind regards Xavier de Rauville=C2=A0 Sent from my BlackBerry Passport.