Date: Fri, 13 Oct 2017 02:11:29 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 222233] sysutils/uefi-edk2-bhyve: still requires obsolete GCC 4.8 to build Message-ID: <bug-222233-13-lLjKyeegjl@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-222233-13@https.bugs.freebsd.org/bugzilla/> References: <bug-222233-13@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=3D222233 --- Comment #7 from Peter Grehan <grehan@FreeBSD.org> --- The port builds using gcc49, which is the most recent toolchain explicitly supported in that version of UEFI. However, using the trick of just replacing the gcc soft link when doing the setup (the line "ln -s /usr/local/bin/gcc48 Build/gcc" from the instruction= s at https://people.freebsd.org/~grehan/bhyve_uefi/bhyve-uefi-UDK2014.SP1-build.= txt), I was able to get clean (untested) builds using ports gcc5 (gcc 5.4.0) and = gcc6 (gcc 6.4.0) on a FreeBSD 12-current amd64 machine. It also built clean using ports gcc7 (7.2.0) after applying the one-line pa= tch from the upstream UEFI git commit https://github.com/tianocore/edk2/commit/fe4a28ccbfd33 Perhaps the simplest way forward is to see what if any changes were made upstream to the UEFI build to support gcc5 (possibly none), back-port those= to the bhyve UEFI branch, and cut over to gcc5 after verifying that the result= ant UEFI binary is ok. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-222233-13-lLjKyeegjl>