From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Yonggang Luo <luoyonggang@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [PULL v2 00/22] Build system + misc changes for 2020-10-16
Date: Sat, 17 Oct 2020 18:37:00 +0200 [thread overview]
Message-ID: <04d2d02d-e5c0-ac69-1de5-f3d7bac32883@redhat.com> (raw)
In-Reply-To: <03d83be5-db1a-3856-5243-66b0f7bdc724@redhat.com>
On 17/10/20 17:37, Paolo Bonzini wrote:
> On 17/10/20 16:39, Peter Maydell wrote:
>> Library iconv found: NO
>> ../src/meson.build:531: WARNING: iconv required for curses UI but not
>> available, disabling
>
> I'm not sure if that will remove the warning or not, but I'll check (and
> if it does remain, it'll be of the "useful" kind which documents some
> unexpected dependency between options).
Ok, so the warning remains when everything is fixed, though the text is
slightly different (and better):
Library iconv found: NO
Run-time dependency ncursesw found: NO (tried pkgconfig)
Library ncursesw found: YES
Library cursesw found: NO
../src/meson.build:540: WARNING: curses library not usable, disabling
In this case, meson.build warns because curses doesn't always have a .pc
file; therefore when meson.build doesn't find the headers it can't but
proceed without curses suport.
The "library found"/"curses support disabled" situation is a bit
confusing, which is why I've been adding some kind of message for those
few cases in which we cannot just use pkg-config. (The multipath test
is already warning, but those libraries are a bit niche so you probably
don't even have the libraries installed).
Peter, I would like your input on these two things:
1) are you going to pull v3 and I can fix up everything later? Or would
you prefer me to send v4 once the new curses test is reviewed?
2) would you prefer the "library was found but headers weren't" to warn,
issue an informative message, or be completely silent?
Paolo
next prev parent reply other threads:[~2020-10-17 16:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 15:53 [PULL v2 00/22] Build system + misc changes for 2020-10-16 Paolo Bonzini
2020-10-16 15:53 ` [PULL 18/22] meson: Move the detection logic for sphinx to meson Paolo Bonzini
2020-10-17 13:09 ` [PULL v2 00/22] Build system + misc changes for 2020-10-16 Peter Maydell
2020-10-17 13:22 ` Peter Maydell
2020-10-17 13:39 ` Paolo Bonzini
2020-10-17 13:38 ` Paolo Bonzini
2020-10-17 14:39 ` Peter Maydell
2020-10-17 15:37 ` Paolo Bonzini
2020-10-17 16:16 ` 罗勇刚(Yonggang Luo)
2020-10-17 16:37 ` Paolo Bonzini [this message]
2020-10-17 19:48 ` Peter Maydell
2020-10-19 8:12 ` Paolo Bonzini
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=04d2d02d-e5c0-ac69-1de5-f3d7bac32883@redhat.com \
--to=pbonzini@redhat.com \
--cc=kraxel@redhat.com \
--cc=luoyonggang@gmail.com \
--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 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).