Attention is currently required from: Arthur Heymans, Jon Murphy, Jérémy Compostella, Nico Huber.
Subrata Banik has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/81886?usp=email )
Change subject: arch/x86: Prevent .text/.init overlap with older linkers ......................................................................
Patch Set 2:
(2 comments)
Commit Message:
https://review.coreboot.org/c/coreboot/+/81886/comment/e1e87d2a_2554c577 : PS2, Line 11: Default is 1024 bytes (1 KiB)
Ok, let's wait if others have some input on this. I didn't really look into it, just notice the similarity to the other change and don't know what would be a good solution.
for sure, we have discussed the potential W/A or solution by this mean (using a dedicated Kconfig) at https://review.coreboot.org/c/coreboot/+/80337/comments/92c6aaf1_04b9a05b (where Arthur suggested to use `Add a Kconfig for a workaround that adds a fixed number to PROGRAM_SZ that makes all your builds succeed?`)
https://review.coreboot.org/c/coreboot/+/81886/comment/1fb79509_c211461c : PS2, Line 11: (binutils 2.3x)
There's always a chance that a different project can't be built with the same toolchain. That's why coreboot has its reference toolchain, because toolchains aren't always compatible. In the light of this, it seems best if you'd use separate toolchains for coreboot and edk2. Otherwise, you can always hit issues like this.
valid point. we made our learning the hard way. for us it's easy to maintain coreboot sdk for building all projects including EDK2 but it looks like the latest toolchain is not supported in 2022/2023 Intel projects.