From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Charlie Jenkins <charlie@rivosinc.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/pixman: Specify riscv dependency
Date: Sat, 19 Apr 2025 22:39:10 +0200 [thread overview]
Message-ID: <20250419223910.63f7bc85@windsurf> (raw)
In-Reply-To: <20250410-pixman_riscv_dependency-v1-1-25d44d225acc@rivosinc.com>
Hello Charlie,
On Thu, 10 Apr 2025 18:08:26 -0700
Charlie Jenkins <charlie@rivosinc.com> wrote:
> riscv Pixman depends on COMPAT_HWCAP_ISA_V which is available in Linux
> 6.4+, so make Pixman dependent on headers that are at least 6.4.
>
> Signed-off-by: Charlie Jenkins <charlie@rivosinc.com>
Thanks for this patch! Do you have a reference/explanation?
One issue with adding such a dependency is that it needs to be
propagated to ALL reverse dependencies of pixman, and there are a LOT
of them. Like doing this:
diff --git a/pixman/pixman-riscv.c b/pixman/pixman-riscv.c
index 1f0440f..7b44ece 100644
--- a/pixman/pixman-riscv.c
+++ b/pixman/pixman-riscv.c
@@ -44,7 +44,7 @@ detect_cpu_features (void)
{
riscv_cpu_features_t features = 0;
-#if defined(__linux__)
+#if defined(__linux__) && defined(COMPAT_HWCAP_ISA_V)
if (getauxval (AT_HWCAP) & COMPAT_HWCAP_ISA_V)
{
features |= RVV;
In the pixman code base would resolve the build issue, and is I believe
acceptable upstream.
But apparently, the issue is that <sys/auxv.h> doesn't exist at all. In
this case, you can add a meson check for this header file.
Also, it would be nice to indicate in the commit message which version
of pixman introduced the issue, apparently pixman-0.44.0.
Could you respin an updated version, that uses a patch against pixman,
and make sure that patch gets submitted upstream?
Also, indicate in your commit message:
Fixes:
http://autobuild.buildroot.net/results/4ecdf5320716ec8b39f09fde3fcbbdcdb557f8ab/
Thanks a lot!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-04-19 20:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 1:08 [Buildroot] [PATCH] package/pixman: Specify riscv dependency Charlie Jenkins
2025-04-19 20:39 ` Thomas Petazzoni via buildroot [this message]
2025-05-02 11:02 ` Arnout Vandecappelle via buildroot
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=20250419223910.63f7bc85@windsurf \
--to=buildroot@buildroot.org \
--cc=charlie@rivosinc.com \
--cc=thomas.petazzoni@bootlin.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