From: Paul Barker <paul@pbarker.dev>
To: alex.kanavin@gmail.com, openembedded-core@lists.openembedded.org
Cc: Alexander Kanavin <alex@linutronix.de>
Subject: Re: [OE-core] [PATCH] hosttools: force a --no-rosegment option if host ld supports it
Date: Fri, 06 Feb 2026 13:46:33 +0000 [thread overview]
Message-ID: <61610acc7cc5dc3742ea4dec5f1280d226d2494d.camel@pbarker.dev> (raw)
In-Reply-To: <20260206132811.100628-1-alex.kanavin@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]
On Fri, 2026-02-06 at 14:28 +0100, Alexander Kanavin via
lists.openembedded.org wrote:
> From: Alexander Kanavin <alex@linutronix.de>
>
> Please see https://bugzilla.yoctoproject.org/show_bug.cgi?id=16087
> for the tricky, unpleasant details. This is addressing an issue with
> recent Fedora distributions where they can contaminate sstate with
> native executables that don't work when transferred onto alma/rocky 8/9.
>
> [YOCTO #16087]
Hi Alex,
Thanks for working on this, we really appreciate the time is has taken
to investigate!
I think we need a little more detail in the commit message so that it is
understandable if the bugzilla data is ever not accessible. Perhaps just
something along the lines of:
From Fedora 42 onwards, the --rosegment argument is passed to the
linker by default when building native binaries. This triggers
re-arrangement of sections by patchelf, resulting in binaries which
are loaded incorrectly by older kernel versions. These "contaminated"
native binaries end up in sstate and cause build failures when they
are used on older distros such as AlmaLinux 8 & 9 or Rocky Linux 8 &
9.
Best regards,
--
Paul Barker
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
prev parent reply other threads:[~2026-02-06 13:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 13:28 [PATCH] hosttools: force a --no-rosegment option if host ld supports it Alexander Kanavin
2026-02-06 13:46 ` Paul Barker [this message]
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=61610acc7cc5dc3742ea4dec5f1280d226d2494d.camel@pbarker.dev \
--to=paul@pbarker.dev \
--cc=alex.kanavin@gmail.com \
--cc=alex@linutronix.de \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox