From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL v3 00/31] Misc changes for 2016-05-27
Date: Tue, 31 May 2016 13:45:47 +0200 [thread overview]
Message-ID: <57691ead-a650-b97a-e641-d4f358749554@redhat.com> (raw)
In-Reply-To: <CAFEAcA9AfhpbLn=pEJpsMJXSeLzfj+FPbaeKfgJJsSegJomPPg@mail.gmail.com>
On 31/05/2016 10:28, Peter Maydell wrote:
>> > Either there's a bug in the detection of -m16, or your clang version is
>> > too old. What does config.log say?
> The only mention of m16 in the config.log is where it says:
>
> clang -m64 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
> -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings
> -Wmissing-prototypes -fno-strict-aliasing -fno-common
> -fsanitize=undefined -Werror -Wno-string-plus-int
> -Wno-initializer-overrides -Wendif-labels -Wmissing-include-dirs
> -Wempty-body -Wnested-externs -Wformat-security -Wformat-y2k
> -Winit-self -Wignored-qualifiers -Wold-style-definition -Wtype-limits
> -fstack-protector-all -m16 -o config-temp/qemu-conf.exe
> config-temp/qemu-conf.c -m64 -g
> clang: error: unknown argument: '-m16'
Then I suppose your clang version is too old, what is it?
Thanks,
Paolo
next prev parent reply other threads:[~2016-05-31 11:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 16:11 [Qemu-devel] [PULL v3 00/31] Misc changes for 2016-05-27 Paolo Bonzini
2016-05-27 16:11 ` [Qemu-devel] [PULL 23/31] scsi-disk: introduce dma_readv and dma_writev Paolo Bonzini
2016-05-27 16:38 ` [Qemu-devel] [PULL v3 00/31] Misc changes for 2016-05-27 Peter Maydell
2016-05-28 16:49 ` Paolo Bonzini
2016-05-31 8:28 ` Peter Maydell
2016-05-31 11:45 ` Paolo Bonzini [this message]
2016-05-31 11:52 ` Peter Maydell
2016-05-31 12:07 ` Paolo Bonzini
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=57691ead-a650-b97a-e641-d4f358749554@redhat.com \
--to=pbonzini@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).