From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Andrew Jones <drjones@redhat.com>, Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu master build failure
Date: Fri, 16 Mar 2018 19:12:26 +0100 [thread overview]
Message-ID: <c4054b32-b2e1-acd3-52f4-8f7d5c12c2a0@de.ibm.com> (raw)
In-Reply-To: <a876446f-d4a4-4df2-c986-4e45a64b9436@redhat.com>
Does it make sense to have something like
diff --git a/configure b/configure
index 831ebf2..67d7ae3 100755
--- a/configure
+++ b/configure
@@ -552,6 +552,10 @@ else
pwd_is_source_path="n"
fi
+if test -f $source_path\/qemu-version.h -a $pwd_is_source_path = "n" ; then
+error_exit "source path contains a stale configuration, cannot build outside"
+fi
+
check_define() {
cat > $TMPC <<EOF
#if !defined($1)
On 03/16/2018 06:11 PM, Paolo Bonzini wrote:
> On 16/03/2018 18:01, Andrew Jones wrote:
>> Hi Thomas,
>>
>> QEMU master is failing to build on an AArch64 machine with GCC 4.8. I get
>>
>> ...
>> CC qemu-nbd.o
>> /home/drjones/code/qemu/qemu-nbd.c: In function ‘version’:
>> /home/drjones/code/qemu/qemu-nbd.c:133:7: error: expected ‘)’ before ‘QEMU_FULL_VERSION’
>> "%s " QEMU_FULL_VERSION "\n"
>> ^
>> /home/drjones/code/qemu/qemu-nbd.c:139:5: error: format ‘%s’ expects a matching ‘char *’ argument [-Werror=format=]
>> , name);
>> ^
>> cc1: all warnings being treated as errors
>> make: *** [qemu-nbd.o] Error 1
>>
>>
>> Reverting 7e563bfb8 fixes the build. I figured I'd report it now,
>> but I won't have time to look closer until Monday.
>
> You probably have a stray qemu-version.h file somewhere. No worries, I
> was puzzled by the same thing after I applied Thomas's patch. :)
>
> Paolo
>
next prev parent reply other threads:[~2018-03-16 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 17:01 [Qemu-devel] qemu master build failure Andrew Jones
2018-03-16 17:11 ` Paolo Bonzini
2018-03-16 17:20 ` Peter Maydell
2018-03-16 18:12 ` Christian Borntraeger [this message]
2018-03-16 18:22 ` Daniel P. Berrangé
2018-03-16 18:25 ` Peter Maydell
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=c4054b32-b2e1-acd3-52f4-8f7d5c12c2a0@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=drjones@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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).