Hi Maheedhar,
Till 2.10 if we use LD=aarch64-none-elf-ld directly as build command parameter there was no problem with the build but with ENABLE_LTO patch we got build problems.
Ah right I see. Well, if I'm reading the mailing list thread on the patch you linked correctly, before that patch ENABLE_LTO in platform.mk wouldn't have had any effect. So perhaps it was never building with ENABLE_LTO? I tried it locally on v2.10 with ENABLE_LTO on the commandline and the same error came up.
So by the sounds of it ENABLE_LTO is broken anyway. @Chris, any ideas?
Are there any generic recommendations on what to use for LD variable (LD=aarch64-none-elf-gcc & LD=aarch64-none-elf-ld) and any plan further in upstream to fix this issue for ENABLE_LTO case.
I'm pretty sure that the intention is that if you want LTO, then LD=aarch64-none-elf-gcc is the only one that should work. I'll let Chris confirm.
Boyan