Date: Mon, 12 Sep 2022 18:00:09 +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-PJhhpbiyKu@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-263543-39090@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263543 --- Comment #20 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Lorenzo Salvadore from comment #19) My comment #17 is related to what I'd referenced in #2, for sure. I should have referenced #2 explicitly. Agreed that there is no need to revert to gcc11: it has the same issue since the problem with /lib/libgcc_s.so.1 use is on the FreeBSD side of things for aarch64, FreeBSD not matching what gcc has long defined as needed for the likes of libstdc++ use for aarch64. The mismatch for a tier 1 context is unfortunate in my view. Agreed that the addition of the likes of: EXTRA_LDFLAGS+= -Wl,-rpath=${LOCALBASE}/lib/gcc${GCC_DEFAULT} is an additional change. (The specifics would not automatically track potential future USE_GCC= use from what I can tell. I'm not aware of a technique to get general automatic rpath tracking. I had hoped someone would know a way to do so. Otherwise the Makefile content is easy to end up mismatched. This applies to more than EDK2.) I'll need to synchronize my ports environment to have a context to deal with setting up a tested patch based on GCC_DEFAULT. So it may be a while. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-263543-39090-PJhhpbiyKu>