Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <raj.khem@gmail.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 1/7] toolchain/clang-native: Set BUILD_LDFLAGS instead of LDFLAGS
Date: Fri, 01 Aug 2025 18:13:52 +0200	[thread overview]
Message-ID: <DBR837TZX59J.9N2ST9LM6WP2@bootlin.com> (raw)
In-Reply-To: <DBR3USPY34UA.F664WZTD1W0R@bootlin.com>

On Fri Aug 1, 2025 at 2:54 PM CEST, Mathieu Dubois-Briand wrote:
> On Fri Aug 1, 2025 at 6:22 AM CEST, Khem Raj via lists.openembedded.org wrote:
>> BUILD_LDFLAGS is used by other recipes to emit native LDFLAGS
>> into their cmake toolchain files especially in QT layers. it
>> will usually be inherited by recipes wanting clang provide
>> BUILD_* variables so this is more appropriate than LDFLAGS to
>> pass these options.
>>
>> Signed-off-by: Khem Raj <raj.khem@gmail.com>
>> ---
>
> Hi Khem,
>
> It looks like something in there is breaking the reproducibility:
>
> AssertionError: The following deb packages are different and not in exclusion list:
> /srv/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB-extended/tmp/deploy/deb/./core2-64/clang-dev_20.1.8-r0_amd64.deb
> The following ipk packages are different and not in exclusion list:
> /srv/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB-extended/tmp/deploy/ipk/./core2-64/clang-dev_20.1.8-r0_core2-64.ipk
> The following rpm packages are different and not in exclusion list:
> /srv/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB-extended/tmp/deploy/rpm/./core2_64/clang-dev-20.1.8-r0.core2_64.rpm
>
>
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/37/builds/2205
> https://valkyrie.yocto.io/pub/repro-fail/oe-reproducible-20250801-t697t4fj/packages/diff-html/
>
> Can you have a look at this?

I did a rebuild of this one and is succeed. So either we have an
intermittent fail or some cache issue, not really sure...

https://autobuilder.yoctoproject.org/valkyrie/#/builders/37/builds/2210


-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2025-08-01 16:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-01  4:22 [PATCH 1/7] toolchain/clang-native: Set BUILD_LDFLAGS instead of LDFLAGS Khem Raj
2025-08-01  4:22 ` [PATCH 2/7] cargo-c: Update patches to latest versions Khem Raj
2025-08-01  4:22 ` [PATCH 3/7] libxcrypt: Allow undefined symbols in version scripts with lld linker Khem Raj
2025-08-07  9:57   ` [OE-core] " Alexander Kanavin
2025-08-07 20:18     ` Khem Raj
2025-08-11  8:17       ` Alexander Kanavin
2025-08-11 15:23         ` Khem Raj
2025-08-01  4:22 ` [PATCH 4/7] libtirpc: " Khem Raj
2025-08-01  4:22 ` [PATCH 5/7] gzip: Always use GNU ld for linking Khem Raj
2025-08-11 16:47   ` [OE-core] " Randy MacLeod
2025-08-01  4:22 ` [PATCH 6/7] binutils-cross-canadian: Always use GNU linker Khem Raj
2025-08-01  4:22 ` [PATCH 7/7] fmt: Fix build with clang-21 Khem Raj
2025-08-01 12:54 ` [OE-core] [PATCH 1/7] toolchain/clang-native: Set BUILD_LDFLAGS instead of LDFLAGS Mathieu Dubois-Briand
2025-08-01 16:13   ` Mathieu Dubois-Briand [this message]
2025-08-01 16:24     ` Khem Raj

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=DBR837TZX59J.9N2ST9LM6WP2@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.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