From: Denys Dmytriyenko <denis@denix.org>
To: meta-arago@lists.yoctoproject.org
Cc: Denys Dmytriyenko <denys@konsulko.com>
Subject: [master][PATCH] ti-llvm: adopt an LLVM fix for buildpaths errors
Date: Mon, 15 Jul 2024 21:50:13 -0400 [thread overview]
Message-ID: <20240716015013.3051611-2-denis@denix.org> (raw)
In-Reply-To: <20240716015013.3051611-1-denis@denix.org>
From: Denys Dmytriyenko <denys@konsulko.com>
Make sure llvm-configs doesn't have absolute build paths.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
---
| 5 +++++
1 file changed, 5 insertions(+)
--git a/meta-arago-extras/recipes-core/llvm/ti-llvm3.6_3.6.bb b/meta-arago-extras/recipes-core/llvm/ti-llvm3.6_3.6.bb
index 4b990b7f..810c603b 100644
--- a/meta-arago-extras/recipes-core/llvm/ti-llvm3.6_3.6.bb
+++ b/meta-arago-extras/recipes-core/llvm/ti-llvm3.6_3.6.bb
@@ -62,6 +62,11 @@ EXTRA_OECONF += " --enable-targets="host,arm,c6000,msp430" \
EXTRA_OEMAKE += "LIBXML2_INC="${LIBXML2_INC}" LIBXML2_LIBS="${LIBXML2_LIBS}""
+# patch out build host paths for reproducibility
+do_compile:prepend() {
+ sed -i -e "s,${WORKDIR},,g" ${LLVM_BUILD_DIR}/tools/llvm-config/Release/BuildVariables.inc
+}
+
do_compile:class-native() {
cd ${LLVM_BUILD_DIR}
--
2.25.1
next prev parent reply other threads:[~2024-07-16 1:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 1:50 [master][PATCH] arago.conf: disable buildpaths QA errors in meta-qt5 Denys Dmytriyenko
2024-07-16 1:50 ` Denys Dmytriyenko [this message]
2024-07-17 0:37 ` [meta-arago] [master][PATCH] ti-llvm: adopt an LLVM fix for buildpaths errors Ryan Eatmon
[not found] ` <17E2D909CD64B7EE.6764@lists.yoctoproject.org>
2024-07-17 1:36 ` Ryan Eatmon
[not found] ` <17E2DC4752C1D1A6.6764@lists.yoctoproject.org>
2024-07-17 13:45 ` Ryan Eatmon
2024-07-17 16:56 ` Denys Dmytriyenko
2024-07-17 17:03 ` Ryan Eatmon
2024-07-17 17:16 ` Denys Dmytriyenko
2024-07-16 14:22 ` [meta-arago] [master][PATCH] arago.conf: disable buildpaths QA errors in meta-qt5 Ryan Eatmon
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=20240716015013.3051611-2-denis@denix.org \
--to=denis@denix.org \
--cc=denys@konsulko.com \
--cc=meta-arago@lists.yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.