From: XJDHDR <derauville.xavier@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Can't compile QEMU 2.5.0 on Arch Linux ARM
Date: Sun, 28 Feb 2016 22:05:01 +0200 [thread overview]
Message-ID: <20160228200501.4792399.20857.198@gmail.com> (raw)
In-Reply-To: <CAFEAcA8U9HxXFS5nozjSNcrS0OyXv9nAScLqcDREUvt4M18AmA@mail.gmail.com>
>> {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 target
>> 'hw/display/qxl.o' failed
>> make: *** [hw/display/qxl.o] Error 1
>> ==> 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?
Thank you for 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 what is causing me problems. I might test this or I might simply not bother with Spice.
Kind regards
Xavier de Rauville
Sent from my BlackBerry Passport.
prev parent reply other threads:[~2016-02-28 20:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-21 10:30 [Qemu-devel] Can't compile QEMU 2.5.0 on Arch Linux ARM Xavier de Rauville
2016-02-21 15:43 ` Peter Maydell
2016-02-28 20:05 ` XJDHDR [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160228200501.4792399.20857.198@gmail.com \
--to=derauville.xavier@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.