public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Jörg Sommer" <joerg.sommer@navimatix.de>
To: openembedded-core@lists.openembedded.org
Cc: changqing.li@windriver.com, rs@ti.com,
	 ricardo.salveti@oss.qualcomm.com, raj.khem@gmail.com,
	antonin.godard@bootlin.com,  richard.purdie@linuxfoundation.org
Subject: Re: [OE-core] [PATCH] lto.inc: add DEBUG_PREFIX_MAP back to TARGET_LDFLAGS
Date: Sat, 28 Mar 2026 21:26:54 +0100	[thread overview]
Message-ID: <acg3xGOKkL769U3e@navimatix.de> (raw)
In-Reply-To: <20260204052638.284617-1-changqing.li@windriver.com>

[-- Attachment #1: Type: text/plain, Size: 1789 bytes --]

Changqing Li via lists.openembedded.org schrieb am Mi 04. Feb, 13:26 (+0800):
> From: Changqing Li <changqing.li@windriver.com>
> 
> DEBUG_PREFIX_MAP is appended to TARGET_LDFLAGS in commit [1] for fixing
> reproducible issue when LTO is enabled. It is removed in comit [2] since
> this commit causes cgo binary not reproducible. But actually, we still
> need this DEBUG_PREFIX_MAP in LDFLAGS when LTO enabled. So, only appened
> it when LTO is enabled. Refer [3] for the history, with this patch,
> patch [4] is also needed for cgo + lto enabled.

Gentle ping. This patch is missing, otherwise QA check buildpaths matches in
nearly all packages.

But this still leaves some packages with buildpaths, because there's a bug
in gcc that it does not apply -ffile-prefix-map:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=124581

> diff --git a/meta/conf/distro/include/lto.inc b/meta/conf/distro/include/lto.inc
> index 227f0c5c2a..cef92901e3 100644
> --- a/meta/conf/distro/include/lto.inc
> +++ b/meta/conf/distro/include/lto.inc
> @@ -49,5 +49,6 @@ LTO:toolchain-clang = "${@bb.utils.contains('DISTRO_FEATURES', 'thin-lto', '-flt
>  
>  SELECTED_OPTIMIZATION:append = "${@bb.utils.contains('DISTRO_FEATURES', 'lto', ' ${LTO}', '', d)}"
>  TARGET_LDFLAGS:append:class-target = "${@bb.utils.contains('DISTRO_FEATURES', 'lto', ' ${LTO}', '', d)}"
> +TARGET_LDFLAGS:append:class-target = "${@bb.utils.contains('DISTRO_FEATURES', 'lto', ' ${DEBUG_PREFIX_MAP}', '', d)}"

Possibly, I would join these lines.


Best regards Jörg

-- 
Navimatix GmbH           T: 03641 - 327 99 0
Tatzendpromenade 2       F: 03641 - 526 306
07745 Jena               www.navimatix.de

Geschäftsführer: Steffen Späthe, Jan Rommeley
Registergericht: Amtsgericht Jena, HRB 501480

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5000 bytes --]

  parent reply	other threads:[~2026-03-28 20:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-04  5:26 [PATCH] lto.inc: add DEBUG_PREFIX_MAP back to TARGET_LDFLAGS changqing.li
2026-02-04  9:34 ` Richard Purdie
2026-02-04 18:17 ` Ricardo de Araujo (Salveti)
2026-02-04 22:34   ` Richard Purdie
2026-03-28 20:26 ` Jörg Sommer [this message]
2026-03-30  9:59   ` [OE-core] " Thomas Perrot
2026-03-30 10:18     ` Richard Purdie
2026-03-30 10:23       ` Jörg Sommer
2026-03-30 10:50         ` Richard Purdie

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=acg3xGOKkL769U3e@navimatix.de \
    --to=joerg.sommer@navimatix.de \
    --cc=antonin.godard@bootlin.com \
    --cc=changqing.li@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=ricardo.salveti@oss.qualcomm.com \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=rs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox