[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKXUXMxNc4iObjL+8RyJN=Kcy5X1r21ez_05oAuy93J=gQ2gZw@mail.gmail.com>
Date: Fri, 13 Jan 2023 12:50:05 +0100
From: Lukas Bulwahn <lukas.bulwahn@...il.com>
To: linux-efi@...r.kernel.org, Ard Biesheuvel <ardb@...nel.org>
Cc: Catalin Marinas <catalin.marinas@....com>,
Jeremy Linton <jeremy.linton@....com>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: linker problem with Ubuntu 18.04 tool chain: unknown architecture of
input file `arch/arm64/boot/vmlinuz.o' is incompatible with aarch64 output
Dear Ard,
with my Ubuntu 18.04 arm gcc tool chain, I encounter this linker error
in my allyesconfig build:
LD arch/arm64/boot/vmlinuz.efi.elf
aarch64-linux-gnu-ld: unknown architecture of input file
`arch/arm64/boot/vmlinuz.o' is incompatible with aarch64 output
drivers/firmware/efi/libstub/Makefile.zboot:41: recipe for target
'arch/arm64/boot/vmlinuz.efi.elf' failed
make[1]: *** [arch/arm64/boot/vmlinuz.efi.elf] Error 1
arch/arm64/Makefile:173: recipe for target 'vmlinuz.efi' failed
make: *** [vmlinuz.efi] Error 2
I bisected it back to happen since commit c37b830fef13 ("arm64: efi:
enable generic EFI compressed boot"), and it still appears with the
latest next-20230113 (on linux-next, I have to remove DRM_MSM as it
currently comes with a build error).
The specific compiler and linker versions on my system are:
$ aarch64-linux-gnu-ld --version
GNU ld (GNU Binutils for Ubuntu) 2.30
$ aarch64-linux-gnu-gcc --version
aarch64-linux-gnu-gcc (Ubuntu/Linaro 7.5.0-3ubuntu1~18.04) 7.5.0
IMHO, I run pretty standard commands:
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j 32 mrproper
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j 32 allyesconfig
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j 32 all
Let me know if you need more information.
Best regards,
Lukas
Powered by blists - more mailing lists