Date: Mon, 12 Sep 2022 10:54:36 +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-Gxiy9HkNev@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 #19 from Lorenzo Salvadore <salvadore@freebsd.org> --- (In reply to Mark Millard from comment #18) Thanks Mark. Unfortunately, I could not test the patch on aarch64 too, however it seems = to me that the problem you are referencing is not related to the last commit as - you already referenced it in comment #2 (it is the same, am I wrong?) and= it is maybe also the same that Emmanuel has referenced in comment #15; - the same error seems to have already been reported by pkg-fallout at https://lists.freebsd.org/archives/freebsd-uboot/2022-September/000273.html= , which is before last commit. So I think that as far as the last commit is involved, things are still fin= e. If they are not, we can always revert the commit and put USE_GCC=3D11 so th= at this port does not block the GCC_DEFAULT upgrade. If I understood correctly comment #2, adding EXTRA_LDFLAGS+=3D -Wl,-rpath=3D${LOCALBASE}/lib/gcc${GCC_DEFAULT} fixes the issue. May I enco= urage you to open a new bug report and submit a patch with your fix? --=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-Gxiy9HkNev>