From: David F Barrera <dfbp@us.ibm.com>
To: xen-devel@lists.xensource.com
Subject: Build break -cc1: error: unrecognized option `-Wdeclaration-after-statement'
Date: Tue, 22 Nov 2005 15:07:27 -0600 [thread overview]
Message-ID: <4383888F.1030406@us.ibm.com> (raw)
Unable to build Xen on x86_64 machine:
changeset: 7974:393256b2ead0
tag: tip
user: smh22@firebug.cl.cam.ac.uk
date: Tue Nov 22 12:10:50 2005 +0100
summary: Avoid GPF when attempting to save / restore 64bit guests.
More thought
make[4]: Entering directory `/tmp/xen-unstable.hg/xen/tools'
gcc -Wall -Werror -Wstrict-prototypes -O2 -fomit-frame-pointer
-Wdeclaration-after-statement -o symbols symbols.c
cc1: error: unrecognized option `-Wdeclaration-after-statement'
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
next reply other threads:[~2005-11-22 21:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 21:07 David F Barrera [this message]
2005-11-22 21:39 ` Build break -cc1: error: unrecognized option `-Wdeclaration-after-statement' Jerone Young
-- strict thread matches above, loose matches on Subject: below --
2005-11-22 23:21 Build break -cc1: error: unrecognized option`-Wdeclaration-after-statement' Rozas, Carlos V
2005-11-23 8:51 ` Keir Fraser
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=4383888F.1030406@us.ibm.com \
--to=dfbp@us.ibm.com \
--cc=xen-devel@lists.xensource.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 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.