GCC 10: Failure to find symbols

[shenki]

Using https://github.com/shenki/op-build/commits/kernel-5.15.28-buildroot-2022.02 that uses GCC 10 and has some other fixes, we hit an error when linking:

    LINKER     hbibl.bin
    LD         hbicore.elf
    LD         hbicore_test.elf
    LINKER     hbirt.bin
    LINKER     hbirt_test.bin
    LINKER     securerom.bin
addimgid IMAGE=../img/securerom.bin imgbase=securerom.bin addressStr EMPTY! SKIP this IMAGE, looking for hbi_ImageId from ../img/securerom.elf
addimgid IMAGE=../img/hbibl.bin imgbase=hbibl.bin addressStrFWLong EMPTY! SKIP for hbi_FWId_long from ../img/hbibl.elf
addimgid IMAGE=../img/hbibl.bin imgbase=hbibl.bin addressStrFWShort EMPTY! SKIP for hbi_FWId_short from ../img/hbibl.elf
39+0 records in
39+0 records out
39 bytes copied, 0.000110702 s, 352 kB/s
addimgid DONE working on IMAGE=../img/hbibl.bin imgbase=hbibl.bin ONLY had imagdId, NO extendedImageIds
    LINKER     hbicore.bin
    LINKER     hbicore_test.bin
exception caught: Could not find symbol _ZN3mss3exp3i2c6fields10BOOT_STAGEE while linking ../img/libexpaccess_rt.so
make[4]: *** [../src/build/mkrules/images.rules.mk:54: ../img/hbirt.bin] Error 255
make[4]: *** Waiting for unfinished jobs....
exception caught: Could not find symbol _ZN3mss3exp3i2c6fields10BOOT_STAGEE while linking ../img/libexpaccess_rt.so
make[4]: *** [../src/build/mkrules/images.rules.mk:54: ../img/hbirt_test.bin] Error 255
exception caught: Could not find symbol _ZN3mss3exp3i2c6fields15ADAPTATION_MODEE while linking ../img/libisteps_mss.so
make[4]: *** [../src/build/mkrules/images.rules.mk:54: ../img/hbicore.bin] Error 255
exception caught: Could not find symbol _ZN3mss3exp3i2c6fields15ADAPTATION_MODEE while linking ../img/libisteps_mss.so

$ c++filt  _ZN3mss3exp3i2c6fields15ADAPTATION_MODEE
mss::exp::i2c::fields::ADAPTATION_MODE

$ c++filt _ZN3mss3exp3i2c6fields10BOOT_STAGEE
mss::exp::i2c::fields::BOOT_STAGE

[dcrowell77]

We will work on supporting compilers past what is used now as time allows, but there is likely not much time to do so in the near future. If you can get it working I'll take a look at a patch. :-)