From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Pierrick Bouvier <pierrick.bouvier@linaro.org>, qemu-devel@nongnu.org
Cc: "Richard Henderson" <richard.henderson@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
berrange@redhat.com, thuth@redhat.com,
"Peter Maydell" <peter.maydell@linaro.org>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH 1/6] meson: build target libraries with common dependencies
Date: Fri, 16 May 2025 12:42:38 +0100 [thread overview]
Message-ID: <8e6cdcb9-24f8-4762-831b-ce57f6e81b20@linaro.org> (raw)
In-Reply-To: <20250516052708.930928-2-pierrick.bouvier@linaro.org>
On 16/5/25 07:27, Pierrick Bouvier wrote:
> As mentioned in 20250513115637.184940-1-thuth@redhat.com, dependencies
Use LORE link instead?
https://lore.kernel.org/qemu-devel/20250513115637.184940-1-thuth@redhat.com/
> were missing when compiling per target libraries, thus breaking
> compilation on certain host systems.
>
> We now explicitely add common dependencies to those libraries, so it
"explicitly"?
> solves the problem.
>
Should we use the following tag?
Fixes: 6f4e8a92bbd ("hw/arm: make most of the compilation units common")
> Signed-off-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>
> ---
> meson.build | 21 ++++++++++++++++-----
> 1 file changed, 16 insertions(+), 5 deletions(-)
next prev parent reply other threads:[~2025-05-16 11:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 5:27 [PATCH 0/6] single-binary: build target common libraries with dependencies Pierrick Bouvier
2025-05-16 5:27 ` [PATCH 1/6] meson: build target libraries with common dependencies Pierrick Bouvier
2025-05-16 11:42 ` Philippe Mathieu-Daudé [this message]
2025-05-16 14:34 ` Pierrick Bouvier
2025-05-17 15:00 ` Paolo Bonzini
2025-05-17 19:37 ` Pierrick Bouvier
2025-05-16 5:27 ` [PATCH 2/6] hw/arm: remove explicit dependencies listed Pierrick Bouvier
2025-05-16 5:27 ` [PATCH 3/6] target/arm: " Pierrick Bouvier
2025-05-16 5:27 ` [PATCH 4/6] meson: apply target config for picking files from lib{system, user} Pierrick Bouvier
2025-05-16 5:27 ` [PATCH 5/6] meson: merge lib{system, user}_ss with {system, user}_ss Pierrick Bouvier
2025-05-17 15:04 ` Paolo Bonzini
2025-05-17 19:34 ` Pierrick Bouvier
2025-05-16 5:27 ` [PATCH 6/6] meson: remove lib{system, user}_ss aliases Pierrick Bouvier
2025-05-16 5:40 ` [PATCH 0/6] single-binary: build target common libraries with dependencies Pierrick Bouvier
2025-05-16 7:24 ` Thomas Huth
2025-05-21 22:38 ` Pierrick Bouvier
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=8e6cdcb9-24f8-4762-831b-ce57f6e81b20@linaro.org \
--to=philmd@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).