Skip to contentSkip to conversation

classes/toolchain/clang: Add placeholder for dynamic linker in cross-canadian packages

PATCH Superseded Khem Raj 2 participants 3 messages Oct 18, 2025 – Oct 24, 2025

v1 of 2 Superseded Latest is v2 →

lore
Share & tools
lore

Khem Raj

author
#0 lore raw

PATCH 1/1 classes/toolchain/clang: Add placeholder for dynamic linker in cross-canadian packages

clang-cross-canadian is just symlinking into nativesdk-clang unlike gcc which has separate binaries and they have inbuilt dynamic linker specs. To help clang built cross-canadian binaries add it via cmdline option here, cross-canadian binaries are only usable on installed SDKs, and these paths get re-written with correct SDK specific linker during SDK install relocation process.

This helps clang built cross-canadian tools e.g. from binutils-cross-canadian be relocated correctly on SDK install.

---
 meta/classes/toolchain/clang.bbclass | 1 +
 1 file changed, 1 insertion(+)
meta/classes/toolchain/clang.bbclass +1 -0
index b4a1c180f6a..9c1204171fe 100644
@@ -32,6 +32,7 @@ TUNE_CCARGS += "${@bb.utils.contains("DISTRO_FEATURES", "usrmerge", " --dyld-pre
 
 LDFLAGS:append:class-nativesdk:x86-64 = " -Wl,-dynamic-linker,${base_libdir}/ld-linux-x86-64.so.2"
 LDFLAGS:append:class-nativesdk:aarch64 = " -Wl,-dynamic-linker,${base_libdir}/ld-linux-aarch64.so.1"
+LDFLAGS:append:class-cross-canadian = " -Wl,-dynamic-linker,${base_libdir}/ld-linux-x86-64.so.2"
 
 # do_populate_sysroot needs STRIP, do_package_qa needs OBJDUMP
 POPULATESYSROOTDEPS:append:class-target = " llvm-native:do_populate_sysroot"
#1 lore raw
Quoted 21 lines · Khem Raj via lists.openembedded.org

clang-cross-canadian is just symlinking into nativesdk-clang unlike gcc which has separate binaries and they have inbuilt dynamic linker specs. To help clang built cross-canadian binaries add it via cmdline option here, cross-canadian binaries are only usable on installed SDKs, and these paths get re-written with correct SDK specific linker during SDK install relocation process.

This helps clang built cross-canadian tools e.g. from binutils-cross-canadian be relocated correctly on SDK install.

---
meta/classes/toolchain/clang.bbclass | 1 +

1 file changed, 1 insertion(+)
meta/classes/toolchain/clang.bbclass +0 -0
index b4a1c180f6a..9c1204171fe 100644
@@ -32,6 +32,7 @@ TUNE_CCARGS += "${@bb.utils.contains("DISTRO_FEATURES", "usrmerge", " --dyld-pre
 
Quoted 3 lines

LDFLAGS:append:class-nativesdk:x86-64 = " -Wl,-dynamic-linker,${base_libdir}/ld-linux-x86-64.so.2" LDFLAGS:append:class-nativesdk:aarch64 = " -Wl,-dynamic-linker,${base_libdir}/ld-linux-aarch64.so.1" +LDFLAGS:append:class-cross-canadian = " -Wl,-dynamic-linker,${base_libdir}/ld-linux-x86-64.so.2”

You’re missing a second line and arch overrides for aarch64, yes?

Ross

author
#2 lore raw
Quoted 23 lines · Ross Burton
Quoted 21 lines · Khem Raj via lists.openembedded.org

clang-cross-canadian is just symlinking into nativesdk-clang unlike gcc which has separate binaries and they have inbuilt dynamic linker specs. To help clang built cross-canadian binaries add it via cmdline option here, cross-canadian binaries are only usable on installed SDKs, and these paths get re-written with correct SDK specific linker during SDK install relocation process.

This helps clang built cross-canadian tools e.g. from binutils-cross-canadian be relocated correctly on SDK install.

---
meta/classes/toolchain/clang.bbclass | 1 +

1 file changed, 1 insertion(+)
meta/classes/toolchain/clang.bbclass +0 -0
index b4a1c180f6a..9c1204171fe 100644
@@ -32,6 +32,7 @@ TUNE_CCARGS += "${@bb.utils.contains("DISTRO_FEATURES", "usrmerge", " --dyld-pre
 
Quoted 5 lines
Quoted 3 lines

LDFLAGS:append:class-nativesdk:x86-64 = " -Wl,-dynamic-linker,${base_libdir}/ld-linux-x86-64.so.2" LDFLAGS:append:class-nativesdk:aarch64 = " -Wl,-dynamic-linker,${base_libdir}/ld-linux-aarch64.so.1" +LDFLAGS:append:class-cross-canadian = " -Wl,-dynamic-linker,${base_libdir}/ld-linux-x86-64.so.2”

You’re missing a second line and arch overrides for aarch64, yes?

well no, ldso gets re-written by SDK installer and it does the right thing when it replaces it on arm64 SDK host.

Quoted 2 lines

Ross