maintainer-feedback requested: [Bug 266404] sysutils/edk2: on aarch64, edk2 fails to build for FreeBSD aarch64 libgcc_s.so.1 issues

Bugzilla Automation <bugzilla@FreeBSD.org> has asked freebsd-uboot (Nobody)
<uboot@FreeBSD.org> for maintainer-feedback:
Bug 266404: sysutils/edk2: on aarch64, edk2 fails to build for FreeBSD aarch64
libgcc_s.so.1 issues
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266404



--- Description ---
The new:

https://lists.freebsd.org/archives/freebsd-uboot/2022-September/000295.html

for

[package - 131arm64-default][sysutils/edk2] Failed for edk2-fvp-g202202_1 in
build

shows a failure reason:

ld-elf.so.1: /lib/libgcc_s.so.1: version GCC_4.5.0 required by
/usr/local/lib/gcc11/libstdc++.so.6 not found

Even main does not have GCC_4.5.0 in /lib/libgcc_s.so.1:

# strings /lib/libgcc_s.so.1 | grep GCC_ | more
GCC_3.0
GCC_3.3
GCC_3.3.1
GCC_3.4
GCC_3.4.2
GCC_3.4.4
GCC_3.5
GCC_4.0.0
GCC_4.2.0
GCC_4.3.0
GCC_4.6.0

Until/unless FreeBSD makes /lib/libgcc_s.so.1 have
the symbols that aarch64 gcc/g++/libstdc++ actually
requires under various conditions, it takes linking
against the g++*'s specific

/usr/local/lib/gcc*/libgcc_s.so.1

instead of using

/lib/libgcc_s.so.1

when the activity happens to hit those conditions.
EDK2 and other things around do not always do this.