From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: dbaryshkov@gmail.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v2] mesa: fix QA warnings caused by freedreno tools
Date: Tue, 16 Jul 2024 07:59:11 +0100 [thread overview]
Message-ID: <5d12bc39242bdae7d3d90f7f1a3152dc790c3aea.camel@linuxfoundation.org> (raw)
In-Reply-To: <20240715230539.139514-1-dmitry.baryshkov@linaro.org>
On Tue, 2024-07-16 at 02:05 +0300, Dmitry Baryshkov via lists.openembedded.org wrote:
> Fix following QA warnings / errors
>
> File /usr/bin/afuc-asm in package mesa-tools contains reference to TMPDIR [buildpaths]
> File /usr/bin/afuc-disasm in package mesa-tools contains reference to TMPDIR [buildpaths]
>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---
> ...t-include-rnn_src_path-into-rnn_path.patch | 27 +++++++++++++++++++
> meta/recipes-graphics/mesa/mesa.inc | 1 +
> 2 files changed, 28 insertions(+)
> create mode 100644 meta/recipes-graphics/mesa/files/0001-freedreno-don-t-include-rnn_src_path-into-rnn_path.patch
>
> diff --git a/meta/recipes-graphics/mesa/files/0001-freedreno-don-t-include-rnn_src_path-into-rnn_path.patch b/meta/recipes-graphics/mesa/files/0001-freedreno-don-t-include-rnn_src_path-into-rnn_path.patch
> new file mode 100644
> index 000000000000..2741f87ed00b
> --- /dev/null
> +++ b/meta/recipes-graphics/mesa/files/0001-freedreno-don-t-include-rnn_src_path-into-rnn_path.patch
> @@ -0,0 +1,27 @@
> +From 7a8044621ae7dcba1873a13190ac51a6465937b7 Mon Sep 17 00:00:00 2001
> +From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> +Date: Mon, 15 Jul 2024 22:23:32 +0300
> +Subject: [PATCH] freedreno: don't include rnn_src_path into rnn_path
> +
> +rnn_path gets compiled-in into several tools, which triggers OE QA
> +errors. Remove rnn_src_path from rnn_path.
> +
> +Upstream-Status: Inappropriate [OE-Core QA issue]
> +Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> +---
> + src/freedreno/meson.build | 2 +-
> + 1 file changed, 1 insertion(+), 1 deletion(-)
> +
I'm not sure Inapproriate is the right choice here. I'd say this is an
actual bug in mesa when cross compiling. When cross compiling the build
system shouldn't be putting build paths into target binaries.
We should really discuss this with upstream and see if mesa can avoid
doing this when cross compiling?
Cheers,
Richard
prev parent reply other threads:[~2024-07-16 6:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 23:05 [PATCH v2] mesa: fix QA warnings caused by freedreno tools Dmitry Baryshkov
2024-07-16 6:59 ` Richard Purdie [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=5d12bc39242bdae7d3d90f7f1a3152dc790c3aea.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=dbaryshkov@gmail.com \
--cc=openembedded-core@lists.openembedded.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