From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Samuel Thibault <samuel.thibault@gnu.org>
Cc: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL 6/6] curses: Use cursesw instead of curses
Date: Wed, 2 Nov 2016 10:09:00 +0100 [thread overview]
Message-ID: <20161102100900.3fd97bff.cornelia.huck@de.ibm.com> (raw)
In-Reply-To: <20161031153929.GK11941@var.home>
On Mon, 31 Oct 2016 16:39:29 +0100
Samuel Thibault <samuel.thibault@gnu.org> wrote:
> Cornelia Huck, on Mon 31 Oct 2016 14:08:48 +0100, wrote:
> > On Mon, 31 Oct 2016 15:03:33 +0100
> > Samuel Thibault <samuel.thibault@gnu.org> wrote:
> >
> > > Cornelia Huck, on Mon 31 Oct 2016 13:48:01 +0100, wrote:
> > > > On Mon, 31 Oct 2016 13:39:30 +0100
> > > > Samuel Thibault <samuel.thibault@gnu.org> wrote:
> > > >
> > > > > Cornelia Huck, on Mon 31 Oct 2016 13:08:06 +0100, wrote:
> > > > > > You mean in configure, right? Including cursesw.h in the test program
> > > > > > gets configure going again.
> > > > >
> > > > > Could you try the attached patch which fixes both configure and
> > > > > ui/curses.c?
> > > >
> > > > Sadly, this does not fix it for me. I get the same errors in the
> > > > configure test build as before.
> > >
> > > Could you post the config.log so we get a better view at what is going
> > > wrong?
> >
> > Attached.
>
> > cc -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 -fwrapv -Wendif-labels -Wmissing-include-dirs -Wempty-body -Wnested-externs -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wold-style-declaration -Wold-style-definition -Wtype-limits -fstack-protector-all -I/usr/include/libpng16 -o config-temp/qemu-conf.exe config-temp/qemu-conf.c -m64 -g
> > config-temp/qemu-conf.c: In function ‘main’:
> > config-temp/qemu-conf.c:13:3: warning: implicit declaration of function ‘addwstr’ [-Wimplicit-function-declaration]
> ...
> > cc -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 -fwrapv -Wendif-labels -Wmissing-include-dirs -Wempty-body -Wnested-externs -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wold-style-declaration -Wold-style-definition -Wtype-limits -fstack-protector-all -I/usr/include/libpng16 -o config-temp/qemu-conf.exe config-temp/qemu-conf.c -m64 -g -lncursesw
> > config-temp/qemu-conf.c: In function ‘main’:
> > config-temp/qemu-conf.c:13:3: warning: implicit declaration of function ‘addwstr’ [-Wimplicit-function-declaration]
> ...
> > cc -Werror -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 -fwrapv -Wendif-labels -Wmissing-include-dirs -Wempty-body -Wnested-externs -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wold-style-declaration -Wold-style-definition -Wtype-limits -fstack-protector-all -I/usr/include/libpng16 -o config-temp/qemu-conf.exe config-temp/qemu-conf.c -m64 -g -lncursesw
> > config-temp/qemu-conf.c: In function ‘main’:
> > config-temp/qemu-conf.c:13:3: error: implicit declaration of function ‘addwstr’ [-Werror=implicit-function-declaration]
> > addwstr(L"wide chars\n");
> > ^
> > config-temp/qemu-conf.c:13:3: error: nested extern declaration of ‘addwstr’ [-Werror=nested-externs]
> > config-temp/qemu-conf.c:14:3: error: implicit declaration of function ‘addnwstr’ [-Werror=implicit-function-declaration]
> > addnwstr(&wch, 1);
> > ^
> > config-temp/qemu-conf.c:14:3: error: nested extern declaration of ‘addnwstr’ [-Werror=nested-externs]
> > cc1: all warnings being treated as errors
>
> These are expected
>
> But doesn't configure also try with -DCONFIG_CURSESW_H? Does it really
> stop here?
Nothing more going on there. Maybe it is because it cannot pull the
relevant flags from pkg_config?
next prev parent reply other threads:[~2016-11-02 9:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 12:11 [Qemu-devel] [PULL 0/6] ui patch queue Gerd Hoffmann
2016-10-28 12:11 ` [Qemu-devel] [PULL 1/6] Add dots keypresses support to the baum braille device Gerd Hoffmann
2016-10-28 12:11 ` [Qemu-devel] [PULL 2/6] Defer BrlAPI tty acquisition to when guest starts using device Gerd Hoffmann
2016-10-28 12:11 ` [Qemu-devel] [PULL 3/6] gtk: fix compilation warning with gtk 3.22.2 Gerd Hoffmann
2016-10-28 12:11 ` [Qemu-devel] [PULL 4/6] ui/gtk: Fix non-working DELETE key Gerd Hoffmann
2016-10-28 12:11 ` [Qemu-devel] [PULL 5/6] curses: fix left/right arrow translation Gerd Hoffmann
2016-10-28 12:11 ` [Qemu-devel] [PULL 6/6] curses: Use cursesw instead of curses Gerd Hoffmann
2016-10-31 11:45 ` Cornelia Huck
2016-10-31 12:01 ` Samuel Thibault
2016-10-31 12:05 ` Samuel Thibault
2016-10-31 12:08 ` Cornelia Huck
2016-10-31 12:16 ` Samuel Thibault
2016-10-31 12:39 ` Samuel Thibault
2016-10-31 12:48 ` Cornelia Huck
2016-10-31 14:03 ` Samuel Thibault
2016-10-31 13:08 ` Cornelia Huck
2016-10-31 15:39 ` Samuel Thibault
2016-11-02 9:09 ` Cornelia Huck [this message]
2016-10-28 17:55 ` [Qemu-devel] [PULL 0/6] ui patch queue 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=20161102100900.3fd97bff.cornelia.huck@de.ibm.com \
--to=cornelia.huck@de.ibm.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=samuel.thibault@gnu.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).