EDK2 produces self-contained binary runtime data which do not require GCC at
runtime, but only at build time.
Details
Diff Detail
- Repository
- R11 FreeBSD ports repository
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
Guys, I don't really know who to add as reviewer. As far as I can see that GCC it not required at runtime at all. This seems to be an oversight or relic from the past.
The change was done by the latest update from @fuz if I remember correctly looking a few days ago and I was wondering the same. You can always add Ports Committers to see if anyone helps reviewing.
Unrelated: there's plenty of other ports pulling various versions of gcc or llvm in not needed at run-time so if you want to continue this quest of cleaning this up with ports maintainers that will be much appreciated! :)
This is a regression from:
commit bafbff663ba59c9c6f10acecc3c4b86dee155f43
Author: Alexey <9vlc@proton.me>
Commit: Robert Clausecker <fuz@FreeBSD.org>
sysutils/edk2: update to 2025008
Patch to update EDK2 OVMF firmware package used in bhyve and some ARM
platforms from 2023 to 2025 stable release. New submodules added in
GH_TUPLE, some script for build has been moved to a bash subshell.
BHYVE notices: tiny boot speedup, a bug with crashing on CPU sensor
wmsr from HWiNFO has stopped occurring, a bug with glibc apps crashing
in Linux VMs has stopped occurring, a crash on memtest86+ with more
than 1 vCPU has stopped occurring.
No new bugs seem to have surfaced.
PR: 285554
Tested by: novel
MFH: 2025Q4The value has been changed.
Unrelated: there's plenty of other ports pulling various versions of gcc or llvm in not needed at run-time so if you want to continue this quest of cleaning this up with ports maintainers that will be much appreciated! :)
I will scan my used ports. I must admit that too many committers have a very problematic attitude making it hard to work with.
@fuz , any objections to back this single line out?
No objections, I just committed and had little input into the contents of the patch. Please ask the uboot group.