All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: Ryan Eatmon <reatmon@ti.com>
Cc: meta-arago@lists.yoctoproject.org
Subject: Re: [meta-arago] [master][PATCH] ti-llvm: adopt an LLVM fix for buildpaths errors
Date: Wed, 17 Jul 2024 12:56:38 -0400	[thread overview]
Message-ID: <20240717165638.GD17572@denix.org> (raw)
In-Reply-To: <1de9d49f-4f0b-4f34-b956-02d0acd98290@ti.com>

On Wed, Jul 17, 2024 at 08:45:58AM -0500, Ryan Eatmon wrote:
> 
> 
> On 7/16/2024 8:36 PM, Ryan Eatmon via lists.yoctoproject.org wrote:
> >
> >
> >On 7/16/2024 7:37 PM, Ryan Eatmon via lists.yoctoproject.org wrote:
> >>
> >>
> >>On 7/15/2024 8:50 PM, Denys Dmytriyenko wrote:
> >>>From: Denys Dmytriyenko <denys@konsulko.com>
> >>>
> >>>Make sure llvm-configs doesn't have absolute build paths.
> >>>
> >>>Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
> >>>---
> >>>  meta-arago-extras/recipes-core/llvm/ti-llvm3.6_3.6.bb | 5 +++++
> >>>  1 file changed, 5 insertions(+)
> >>>
> >>>diff --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}
> >>
> >>I'm getting build errors with this.
> >>
> >>native:
> >>
> >>sed: can't read /scratch/jenkins_builds/arago-master-wip/build/build/arago-tmp-default-glibc/work/x86_64-linux/ti-llvm3.6-native/3.6/llvm-3.6.build/tools/llvm-config/Release/BuildVariables.inc:
> >>No such file or directory
> >>
> >>nativesdk:
> >>
> >>sed: can't read /scratch/jenkins_builds/arago-master-wip/build/build/arago-tmp-default-glibc/work/x86_64-nativesdk-arago-linux/nativesdk-ti-llvm3.6/3.6/llvm-3.6.build/tools/llvm-config/Release/BuildVariables.inc:
> >>No such file or directory
> >>
> >
> >I think that during the build it creates this file, but before the
> >builds the files does not exist yet.  Maybe you tested this
> >against a built directory where the file existed but from a clean
> >dir it fails?
> >
> 
> Also, it looks the contents of the BuildVariables.inc might be in a
> "bad" state with this change.  But I could be wrong as I don't know
> how all of this package works.
> 
> #define LLVM_SRC_ROOT "/git"
> #define LLVM_OBJ_ROOT "/llvm-3.6.build"
> 
> By just replacing the WORKDIR with "" we are pointing this file to
> the root directory where I doubt these things will be living.
> Again, without knowing how this package works and uses those two
> variables I can't speak as to the correctness of this.  I agree it
> fixes the buildpaths issue, but does it break the software package
> at that point?

This is exactly what OE-Core does with upstream LLVM.

-- 
Denys


  reply	other threads:[~2024-07-17 16:56 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 ` [master][PATCH] ti-llvm: adopt an LLVM fix for buildpaths errors Denys Dmytriyenko
2024-07-17  0:37   ` [meta-arago] " 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 [this message]
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=20240717165638.GD17572@denix.org \
    --to=denis@denix.org \
    --cc=meta-arago@lists.yoctoproject.org \
    --cc=reatmon@ti.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 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.