qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pierrick Bouvier <pierrick.bouvier@linaro.org>
To: Thomas Huth <thuth@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	qemu-arm@nongnu.org, "Brad Smith" <brad@comstyle.com>
Subject: Re: [PATCH v2] meson.build: Compile hw_common_arch_libs files with right header include paths
Date: Thu, 15 May 2025 17:35:31 -0700	[thread overview]
Message-ID: <1a89a793-1db7-4b3e-926f-fbd390d2f714@linaro.org> (raw)
In-Reply-To: <d1bf2e99-7320-4a20-a5cb-2e7ce70036b8@linaro.org>

On 5/13/25 4:20 PM, Pierrick Bouvier wrote:
> Hi Thomas,
> 
> On 5/13/25 4:56 AM, Thomas Huth wrote:
>> From: Thomas Huth <thuth@redhat.com>
>>
>> Since commit 6f4e8a92bbd ("hw/arm: make most of the compilation units
>> common"), compilation of some arm machines (like musicpal) fails on
>> certain host systems like OpenBSD 7.6/7.7 since headers like <epoxy/gl.h>
>> don't reside in /usr/include and we currently don't add the right
>> CFLAGS for the common files to include the additional header search
>> paths. Add a loop similar to what we already did in commit 727bb5b477e6
>> to fix it.
>>
>> With this fix applied, we can now also drop the explicit dependency
>> on pixman for the arm musicpal machine.
>>
>> Fixes: 6f4e8a92bbd ("hw/arm: make most of the compilation units common")
>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>> [thuth: Add commit message + changes in hw/arm/meson.build]
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>>    v2: Change the subject of the patch according to Paolo's suggestion
>>
>>    meson.build        | 27 ++++++++++++++++-----------
>>    hw/arm/meson.build |  2 +-
>>    2 files changed, 17 insertions(+), 12 deletions(-)
> 
> 
> Thanks for the patch.
> I didn't run into any issue when building for {linux, macos, windows,
> freebsd}, so I assumed it was safe to do things this way and specific
> dependencies could just be listed with associated sources.
> It seems like there are cracks in this approach, so adding all the
> dependencies per base arch is a good idea.
> 
> Any chance you could base it on this commit [1] (and add it for new
> libraries as well)?
> 
> This is going to be pulled very shortly (as part of a wider series), and
> the same fix will be needed.
 > [1] 20250512180502.2395029-4-pierrick.bouvier@linaro.org
>

[1] was merged.
I'm working on a series integrating your work, and doing further 
cleanups on meson side, so you can leave it for now.

Thanks,
Pierrick


  reply	other threads:[~2025-05-16  0:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-13 11:56 [PATCH v2] meson.build: Compile hw_common_arch_libs files with right header include paths Thomas Huth
2025-05-13 23:20 ` Pierrick Bouvier
2025-05-16  0:35   ` Pierrick Bouvier [this message]
2025-05-16  5:28     ` 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=1a89a793-1db7-4b3e-926f-fbd390d2f714@linaro.org \
    --to=pierrick.bouvier@linaro.org \
    --cc=berrange@redhat.com \
    --cc=brad@comstyle.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --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).