From: Paolo Bonzini <pbonzini@redhat.com>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH 3/4] configure: propagate --extra-cflags and --extra-ldflags to meson compile tests
Date: Mon, 8 Nov 2021 12:07:58 +0100 [thread overview]
Message-ID: <9df670af-f338-c537-b03e-0b103c3100df@redhat.com> (raw)
In-Reply-To: <cad11e05-9a0a-fca4-08aa-a0ad31e13496@redhat.com>
On 11/8/21 10:11, Thomas Huth wrote:
>> + EXTRA_CXXFLAGS="$EXTRA_CXXFLAGS $optarg"
>
> I'd rather drop that EXTRA_CXXFLAGS line here - I think that calls for
> trouble otherwise if a user is trying to add a C compiler option that is
> not supported in C++ mode.
> If the users have some options that need to be passed to both, C and
> C++, they should simply use --extra-cxxflags in addition instead.
True, but that is needed to preserve previous behavior, where
QEMU_CXXFLAGS is initialized with QEMU_CFLAGS in update_cxxflags.
update_cxxflags does not do any filtering either, except for some -W
options that shouldn't be in --extra-cflags. So (apart from those -W
options) a C-only option wouldn't have worked before with
--extra-cflags, either.
Paolo
next prev parent reply other threads:[~2021-11-08 11:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 8:43 [PATCH 0/4] configure: propagate --extra-cflags and --extra-ldflags to meson compile tests Paolo Bonzini
2021-11-08 8:43 ` [PATCH 1/4] configure: simplify calls to meson_quote Paolo Bonzini
2021-11-08 9:02 ` Thomas Huth
2021-11-08 8:43 ` [PATCH 2/4] configure: preserve CFLAGS, CXXFLAGS and LDFLAGS in config.status Paolo Bonzini
2021-11-08 9:04 ` Thomas Huth
2021-11-08 8:43 ` [PATCH 3/4] configure: propagate --extra-cflags and --extra-ldflags to meson compile tests Paolo Bonzini
2021-11-08 9:11 ` Thomas Huth
2021-11-08 11:07 ` Paolo Bonzini [this message]
2021-11-08 8:43 ` [PATCH 4/4] configure: ignore preexisting QEMU_*FLAGS envvars Paolo Bonzini
2021-11-08 9:17 ` Thomas Huth
2021-11-08 9:17 ` Philippe Mathieu-Daudé
2021-11-08 10:45 ` 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=9df670af-f338-c537-b03e-0b103c3100df@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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).