From: G 3 <programmingkidx@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.com>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>
Subject: [Qemu-devel] [PATCH] curses: build with -std=gnu99
Date: Thu, 27 Oct 2016 10:51:08 -0400 [thread overview]
Message-ID: <4B74416B-EEBE-408F-B589-41318045938D@gmail.com> (raw)
In-Reply-To: <mailman.13406.1477569887.22738.qemu-devel@nongnu.org>
On Oct 27, 2016, at 8:04 AM, qemu-devel-request@nongnu.org wrote:
> ---
> ui/Makefile.objs | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/ui/Makefile.objs b/ui/Makefile.objs
> index dc936f1..62f4cf3 100644
> --- a/ui/Makefile.objs
> +++ b/ui/Makefile.objs
> @@ -17,6 +17,9 @@ common-obj-$(CONFIG_CURSES) += curses.o
> common-obj-$(CONFIG_VNC) += $(vnc-obj-y)
> common-obj-$(CONFIG_GTK) += gtk.o x_keymap.o
>
> +# needed to make gcc accept wide unicode chars without warning
> +curses.o-cflags := -std=gnu99
> +
> ifeq ($(CONFIG_SDLABI),1.2)
> sdl.mo-objs := sdl.o sdl_zoom.o
> endif
> --
> 1.8.3.1
Could we add a commit message to this patch? It could answer
questions like:
Why this patch is needed?
Who needs this patch?
What problem it solves.
next parent reply other threads:[~2016-10-27 14:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.13406.1477569887.22738.qemu-devel@nongnu.org>
2016-10-27 14:51 ` G 3 [this message]
2016-10-27 15:07 ` [Qemu-devel] [PATCH] curses: build with -std=gnu99 Gerd Hoffmann
2016-10-27 15:12 ` G 3
2016-10-27 11:46 Gerd Hoffmann
2016-10-27 15:04 ` Peter Maydell
2016-10-27 15:55 ` Gerd Hoffmann
2016-10-27 15:58 ` Samuel Thibault
2016-10-27 16:14 ` Peter Maydell
2016-10-27 16:36 ` Samuel Thibault
2016-10-27 16:52 ` Peter Maydell
2016-10-27 17:02 ` Samuel Thibault
2016-10-28 6:51 ` Markus Armbruster
2016-10-28 7:40 ` Samuel Thibault
2016-10-28 8:37 ` Markus Armbruster
2016-10-28 9:45 ` Gerd Hoffmann
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=4B74416B-EEBE-408F-B589-41318045938D@gmail.com \
--to=programmingkidx@gmail.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=samuel.thibault@ens-lyon.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).