From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: Aleksey Laurynovich <alaur@ilbers.de>,
"MOESSBAUER, Felix" <felix.moessbauer@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH] fix: Add toolchain fixes to linux-cip 4.4 kernel on Noble
Date: Thu, 24 Sep 2026 12:02:26 +0200 [thread overview]
Message-ID: <8c2d7b0f-0af9-4702-b5c5-cc2a46e31c59@siemens.com> (raw)
In-Reply-To: <c6c6930b010bb050d99d417231b30a8eb1cc4dd4.camel@ilbers.de>
On 24.09.26 11:58, Aleksey Laurynovich wrote:
> On Wed, 2026-09-23 at 13:49 +0000, MOESSBAUER, Felix wrote:
>> On Wed, 2026-09-23 at 14:03 +0200, Aleksey Laurynovich wrote:
>>> Older kernel (4.4.x) has three toolchain issues on Ubuntu Noble:
>>> - dtc yylloc multiple definition (fixed by HOSTCFLAGS+=-fcommon)
>>> - ld rejects -Wl,-Bsymbolic-functions (fixed by clearing LDFLAGS)
>>> - arm64 proc.S uses deprecated .section syntax rejected by binutils
>>> 2.42
>>> (fixed by patching to use modern 'ax' flags)
>>>
>>> The issue can be reproduced with the command:
>>> $ bitbake mc:qemuarm64-noble:linux-cip-arm64
>>>
>>> Signed-off-by: Aleksey Laurynovich <alaur@ilbers.de>
>>> ---
>>> ...rm64-proc.S-fix-binutils-2.42-section-syntax.patch | 11
>>> +++++++++++
>>> .../recipes-kernel/linux/linux-cip_4.4.166-cip29.bb | 6 ++++++
>>> 2 files changed, 17 insertions(+)
>>> create mode 100644 meta-isar/recipes-kernel/linux/files/0001-
>>> arm64-proc.S-fix-binutils-2.42-section-syntax.patch
>>>
>>> diff --git a/meta-isar/recipes-kernel/linux/files/0001-arm64-
>>> proc.S-fix-binutils-2.42-section-syntax.patch b/meta-isar/recipes-
>>> kernel/linux/files/0001-arm64-proc.S-fix-binutils-2.42-section-
>>> syntax.patch
>>> new file mode 100644
>>> index 00000000..f464ac40
>>> --- /dev/null
>>> +++ b/meta-isar/recipes-kernel/linux/files/0001-arm64-proc.S-fix-
>>> binutils-2.42-section-syntax.patch
>>> @@ -0,0 +1,11 @@
>>> +--- a/arch/arm64/mm/proc.S
>>> ++++ b/arch/arm64/mm/proc.S
>>> +@@ -152,7 +152,7 @@
>>> + alternative_endif
>>> + ENDPROC(cpu_do_switch_mm)
>>> +
>>> +- .section ".text.init", #alloc, #execinstr
>>> ++ .section ".text.init", "ax"
>>> +
>>> + /*
>>> + * __cpu_setup
>>> diff --git a/meta-isar/recipes-kernel/linux/linux-cip_4.4.166-
>>> cip29.bb b/meta-isar/recipes-kernel/linux/linux-cip_4.4.166-
>>> cip29.bb
>>
>> This kernel patch release is quite old. Did you check if v4.4.302-
>> cip99
>> is also affected?
> v4.4.302-cip99 is also affected. It has ld rejects -Wl,-Bsymbolic-
> functions, and arm64 proc.S syntax problems.
>
Then send patches upstream, not to isar, disable this inofficial
configuration, or use a (cip-)kernel that supports it. This is just an
exemplary recipe, not worth being patched.
Jan
--
Siemens AG, Foundational Technologies
Linux Expert Center
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/8c2d7b0f-0af9-4702-b5c5-cc2a46e31c59%40siemens.com.
prev parent reply other threads:[~2026-09-24 10:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 12:03 Aleksey Laurynovich
2026-09-23 13:49 ` 'MOESSBAUER, Felix' via isar-users
2026-09-23 16:21 ` 'Jan Kiszka' via isar-users
2026-09-24 9:58 ` Aleksey Laurynovich
2026-09-24 10:02 ` 'Jan Kiszka' via isar-users [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=8c2d7b0f-0af9-4702-b5c5-cc2a46e31c59@siemens.com \
--to=isar-users@googlegroups.com \
--cc=alaur@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@siemens.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