| Message ID | 20250929171125.2170364-1-ross.burton@arm.com |
|---|---|
| State | New |
| Headers | show |
| Series | [1/4] linux-firmware: skip ldflags sanity check | expand |
diff --git a/meta/recipes-kernel/linux-firmware/linux-firmware_20250917.bb b/meta/recipes-kernel/linux-firmware/linux-firmware_20250917.bb index 5d5a5c8caee..1b9d1571042 100644 --- a/meta/recipes-kernel/linux-firmware/linux-firmware_20250917.bb +++ b/meta/recipes-kernel/linux-firmware/linux-firmware_20250917.bb @@ -2352,7 +2352,10 @@ python populate_packages:prepend () { # Firmware files are generally not ran on the CPU, so they can be # allarch despite being architecture specific -INSANE_SKIP = "arch" +INSANE_SKIP += "arch" + +# They can also be ELF files, but obviously won't have the linkage we expect +INSANE_SKIP += "ldflags" # Don't warn about already stripped files INSANE_SKIP:${PN} = "already-stripped"
Some of the firmware blobs, for example qcom/apq8016/modem.mbn, are actually ELF files. We don't want to hold these to our exacting standard for link flags because we're not building them and they don't run on the target directly. Note that as this check parses the output of ${OBJDUMP} -p it behaves differently with binutils vs llvm. It looks like binutils bails early as it doesn't know what the target architecture is, whereas LLVM is more comprehensive in its support. Signed-off-by: Ross Burton <ross.burton@arm.com> --- .../recipes-kernel/linux-firmware/linux-firmware_20250917.bb | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)