Date: Mon, 12 Sep 2022 01:16:29 +0000 From: bugzilla-noreply@freebsd.org To: uboot@FreeBSD.org Subject: [Bug 263543] sysutils/edk2: Fails to build with GCC > 11 (all flavors) Message-ID: <bug-263543-39090-CLexAfc05I@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-263543-39090@https.bugs.freebsd.org/bugzilla/> References: <bug-263543-39090@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D263543 --- Comment #18 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Lorenzo Salvadore from comment #17) FYI: compile problems are not the only ones around. 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. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-263543-39090-CLexAfc05I>