Path: blob/main/website/content/en/status/report-2022-01-2022-03/gcc.adoc
18096 views
=== lang/gcc* ports need some love and attention Links: + link:https://gcc.gnu.org[GCC Project] URL: link:https://gcc.gnu.org[https://gcc.gnu.org] + link:https://gcc.gnu.org/gcc-11/[GCC 11 release series] URL: link:https://gcc.gnu.org/gcc-11/[https://gcc.gnu.org/gcc-11/] Contact: [email protected] + Contact: Gerald Pfeifer <[email protected]> After about two decades of maintaining FreeBSD's lang/gcc* ports, the time came to hand over the baton and mostly step back. Alas the baton essentially dropped to the floor, despite multiple calls for help. Here are a few specific tasks looking for help: * Upgrade GCC_DEFAULT in Mk/bsd.default-versions.mk from 10 to 11, including fixing the (luckily minor) fall out of an -exp run: link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258378[https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258378] * Three changes to work through with upstream GCC (requires src expertise, not ports): ** upstreaming lang/gcc11/patch-gets-no-more ** upstreaming lang/gcc11/patch-arm-unwind-cxx-support ** link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256874[https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256874] * We have removed the unmaintained lang/gcc9-devel and lang/gcc10-devel ports, alas kept lang/gcc11-devel and lang/gcc12-devel which would be good to see if not weekly, then somewhat regular updates.