From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: thomas.perrot@bootlin.com, openembedded-core@lists.openembedded.org
Cc: thomas.petazzoni@bootlin.com
Subject: Re: [OE-core][PATCH] lto: disable for expect and add DEBUG_PREFIX_MAP to ldflags
Date: Tue, 31 Mar 2026 15:12:25 +0100 [thread overview]
Message-ID: <56e03e1e7a5a7a51fe34ad6b099ff7a7f1afd587.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260331081246.73406-1-thomas.perrot@bootlin.com>
On Tue, 2026-03-31 at 10:12 +0200, Thomas Perrot via
lists.openembedded.org wrote:
> From: Thomas Perrot <thomas.perrot@bootlin.com>
>
> Disable LTO for the expect package and append DEBUG_PREFIX_MAP to
> TARGET_LDFLAGS when LTO is enabled, ensuring debug info remapping
> is applied consistently alongside LTO flags.
>
> Signed-off-by: Thomas Perrot <thomas.perrot@bootlin.com>
> ---
> meta/conf/distro/include/lto.inc | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/conf/distro/include/lto.inc
> b/meta/conf/distro/include/lto.inc
> index 8752249685a4..c66dfc5a8074 100644
> --- a/meta/conf/distro/include/lto.inc
> +++ b/meta/conf/distro/include/lto.inc
> @@ -4,6 +4,7 @@
> #
>
> # Disable LTO for following packages
> +LTO:pn-expect = ""
> LTO:pn-glibc = ""
> LTO:pn-gcc-runtime = ""
> LTO:pn-libgcc-initial = ""
>
Is the commit message still correct for this? it doesn't add
DEBUG_PREFIX_MAP?
Cheers,
Richard
next prev parent reply other threads:[~2026-03-31 14:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 8:12 [OE-core][PATCH] lto: disable for expect and add DEBUG_PREFIX_MAP to ldflags thomas.perrot
2026-03-31 14:12 ` Richard Purdie [this message]
2026-03-31 14:17 ` Thomas Perrot
2026-03-31 15:40 ` Jörg Sommer
2026-03-31 19:45 ` Khem Raj
2026-03-31 20:27 ` Thomas Perrot
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=56e03e1e7a5a7a51fe34ad6b099ff7a7f1afd587.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=thomas.perrot@bootlin.com \
--cc=thomas.petazzoni@bootlin.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