From: Samuel Thibault <samuel.thibault@gnu.org>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Michal Suchanek <msuchanek@suse.de>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] Fix legacy ncurses detection.
Date: Wed, 9 Nov 2016 10:04:02 +0100 [thread overview]
Message-ID: <20161109090402.GF2378@var.home> (raw)
In-Reply-To: <20161109095859.0be2b487.cornelia.huck@de.ibm.com>
Hello,
Cornelia Huck, on Wed 09 Nov 2016 09:58:59 +0100, wrote:
> On Tue, 8 Nov 2016 21:10:19 +0100
> Samuel Thibault <samuel.thibault@gnu.org> wrote:
> > Cornelia Huck, on Tue 08 Nov 2016 12:34:49 +0100, wrote:
> > “
> > configure test passed without -Werror but failed with -Werror.
> > This is probably a bug in the configure script. The failing command
> > will be at the bottom of config.log.
> > You can run configure with --disable-werror to bypass this check.
> > ”
> >
> > If so, you should really have said it, I was really wondering how
> > configure could just stopping in your case. That does explain things
> > indeed.
>
> I said so in my very first mail for the issue... appears I was unclear.
Do you mean "configure barfs about -Werror."?
Yes it was unclear to me :)
> > Could you try the attached patch? It should be able to really fail
> > without Werror too.
>
> With your patch, configure runs through and detects curses=no. Not sure
> that's correct, though: SLES12SP1 _does_ have curses, but not a .pc
> file for ncursesw. I don't know enough about curses to say whether it
> should be that way...
Please post config.log so we can have a clue about what is going
wrong. All these error messages are meant to be reported verbatim, not
reinterpreted :)
Samuel
next prev parent reply other threads:[~2016-11-09 9:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 13:38 [Qemu-devel] [PATCH] Fix legacy ncurses detection Michal Suchanek
2016-11-07 13:55 ` Peter Maydell
2016-11-07 16:26 ` Cornelia Huck
2016-11-07 22:07 ` Samuel Thibault
2016-11-08 11:34 ` Cornelia Huck
2016-11-08 20:10 ` Samuel Thibault
2016-11-09 8:58 ` Cornelia Huck
2016-11-09 9:04 ` Samuel Thibault [this message]
2016-11-09 9:12 ` Cornelia Huck
2016-11-09 9:28 ` Samuel Thibault
2016-11-09 9:40 ` Cornelia Huck
2016-11-09 9:52 ` Samuel Thibault
2016-11-09 10:04 ` Cornelia Huck
2016-11-09 10:15 ` Sergey Smolov
2016-11-09 10:25 ` Samuel Thibault
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=20161109090402.GF2378@var.home \
--to=samuel.thibault@gnu.org \
--cc=cornelia.huck@de.ibm.com \
--cc=msuchanek@suse.de \
--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 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.