Date: Wed, 29 Jan 2025 17:46:31 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 284441] lang/gcc and -static option lead to segfaults Message-ID: <bug-284441-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D284441 Bug ID: 284441 Summary: lang/gcc and -static option lead to segfaults Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: Individual Port(s) Assignee: gerald@FreeBSD.org Reporter: sgk@troutmask.apl.washington.edu Flags: maintainer-feedback?(gerald@FreeBSD.org) Assignee: gerald@FreeBSD.org I recently reported an issue with lang/gcc14 and static linking. The email trail is here: https://lists.freebsd.org/archives/freebsd-hackers/2025-January/004236.html kib has fixed FreeBSD to avoid the issue, and commit a change to top-of-tre= e: https://lists.freebsd.org/archives/dev-commits-src-main/2025-January/029575= .html dim has provided a patch for lang/gcc14 and I've tested that patch with=20 top-of-tree gcc sources. He sent the patch to GCC here: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D118685 If there is soemone involved with the lang/gccXX ports and they have commit access to gcc git repository, you may want to commit the change. For this report, I know lang/gcc14. Other ports may also have a problem. --=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-284441-7788>