From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-stable@nongnu.org
Subject: Re: [PATCH] stubs: avoid duplicate symbols in libqemuutil.a
Date: Thu, 24 Oct 2024 14:34:43 -0300 [thread overview]
Message-ID: <df6dfd5c-ee36-4bca-8632-f0d2443d06ca@linaro.org> (raw)
In-Reply-To: <20241021163449.136804-1-pbonzini@redhat.com>
On 21/10/24 13:34, Paolo Bonzini wrote:
> qapi_event_send_device_deleted is always included (together with the
> rest of QAPI) in libqemuutil.a if either system-mode emulation or tools
> are being built, and in that case the stub causes a duplicate symbol
> to appear in libqemuutil.a.
>
> Add the symbol only if events are not being requested.
>
> Supersedes: <20241018143334.949045-1-pbonzini@redhat.com>
strip ^
> Cc: qemu-stable@nongnu.org
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> v1 fails to build with --disable-system --disable-tools, which I
> have now noticed in CI.
>
> stubs/meson.build | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/stubs/meson.build b/stubs/meson.build
> index 772a3e817df..e91614a874d 100644
> --- a/stubs/meson.build
> +++ b/stubs/meson.build
> @@ -55,7 +55,12 @@ endif
> if have_user
> # Symbols that are used by hw/core.
> stub_ss.add(files('cpu-synchronize-state.c'))
> - stub_ss.add(files('qdev.c'))
> +
> + # Stubs for QAPI events. Those can always be included in the build, but
> + # they are not built at all for --disable-system --disable-tools builds.
> + if not (have_system or have_tools)
> + stub_ss.add(files('qdev.c'))
> + endif
> endif
>
> if have_system
prev parent reply other threads:[~2024-10-24 17:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 16:34 [PATCH] stubs: avoid duplicate symbols in libqemuutil.a Paolo Bonzini
2024-10-24 12:23 ` Alex Bennée
2024-10-24 17:34 ` Philippe Mathieu-Daudé [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=df6dfd5c-ee36-4bca-8632-f0d2443d06ca@linaro.org \
--to=philmd@linaro.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).