Date: Fri, 01 May 2026 02:59:24 +0000 From: bugzilla-noreply@freebsd.org To: testing@FreeBSD.org Subject: [Bug 294881] test failures with FORTIFY_SOURCE=2 Message-ID: <bug-294881-32464-2ii7tFRWAV@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-294881-32464@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=294881 --- Comment #5 from commit-hook@FreeBSD.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=c46a0b590716144d772eeba83ca88d96ee12c2f1 commit c46a0b590716144d772eeba83ca88d96ee12c2f1 Author: Kyle Evans <kevans@FreeBSD.org> AuthorDate: 2026-05-01 02:57:51 +0000 Commit: Kyle Evans <kevans@FreeBSD.org> CommitDate: 2026-05-01 02:58:48 +0000 build: provide a FORTIFY_SOURCE.<src file> override For native files we can do more minimal fixes to avoid this large of a hammer, but for third party files it may not be worth the effort to try and patch them. NetBSD has the original _FORTIFY_SOURCE implementation that ours is based on, for instance, but tests sourced from there can't do an __ssp_real(foo) without being certain that `foo` actually has a fortified definition. This change does always define _FORTIFY_SOURCE as a result, so gate it on CFLAGS not already containing _FORTIFY_SOURCE definitions. PR: 294881 Reviewed by: markj Differential Revision: https://reviews.freebsd.org/D56733 share/mk/bsd.sys.mk | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-294881-32464-2ii7tFRWAV>