From: Stefan Hajnoczi <stefanha@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: Re: [PATCH 0/3] configure: add missing CONFIG_FOO variables
Date: Tue, 15 Sep 2020 11:56:34 +0100 [thread overview]
Message-ID: <20200915105634.GA696537@stefanha-x1.localdomain> (raw)
In-Reply-To: <8cda7b10-1eba-ccfe-1cae-c023fba87553@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 916 bytes --]
On Mon, Sep 14, 2020 at 12:50:23PM +0200, Paolo Bonzini wrote:
> On 14/09/20 11:52, Stefan Hajnoczi wrote:
> > The meson.build feature summary checks the presence of CONFIG_FOO variables.
> > Several of these variables are never emitted by ./configure so the feature
> > summary always shows these features as disabled.
> >
> > Stefan Hajnoczi (3):
> > configure: add missing CONFIG_TCMALLOC
> > configure: add missing CONFIG_JEMALLOC
> > configure: rename QEMU_GA_MSI_ENABLED to CONFIG_QGA_MSI
> >
> > configure | 10 +++++++++-
> > Makefile | 2 +-
> > meson.build | 2 +-
> > 3 files changed, 11 insertions(+), 3 deletions(-)
> >
>
> Thanks!
>
> For 1 and 2 I think it's simpler to move the whole test to Meson. I
> already have a patch for that, though I was going to send it next week.
Great, it's nice to do feature checks in meson instead of ./configure.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-09-15 11:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 9:52 [PATCH 0/3] configure: add missing CONFIG_FOO variables Stefan Hajnoczi
2020-09-14 9:52 ` [PATCH 1/3] configure: add missing CONFIG_TCMALLOC Stefan Hajnoczi
2020-09-14 9:52 ` [PATCH 2/3] configure: add missing CONFIG_JEMALLOC Stefan Hajnoczi
2020-09-14 9:52 ` [PATCH 3/3] configure: rename QEMU_GA_MSI_ENABLED to CONFIG_QGA_MSI Stefan Hajnoczi
2020-09-14 10:50 ` [PATCH 0/3] configure: add missing CONFIG_FOO variables Paolo Bonzini
2020-09-15 10:56 ` Stefan Hajnoczi [this message]
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=20200915105634.GA696537@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--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.