Date: Fri, 10 Mar 2023 11:03:24 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 261952] coredump building www/node16 if kern.elf64.allow_wx=0 Message-ID: <bug-261952-7788-7avyNnE8k3@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-261952-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-261952-7788@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=3D261952 Peter Much <pmc@citylink.dinoex.sub.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pmc@citylink.dinoex.sub.org --- Comment #13 from Peter Much <pmc@citylink.dinoex.sub.org> --- The issue is not fixed in version 16.19.0. Specifically, my problem is not that it does /not build/ with allow_wx=3D0 = (I am building in temporary build instances, security is not of concern there), b= ut that it does /not run/ with allow_wx=3D0. I tried to utilize Uses/elfctl to fix this, but that does not work in this case: Uses/elfctl does tag the binary at the end of the build phase. But then the binary gets relinked during the stage phase, and the tagging is gone again. --=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-261952-7788-7avyNnE8k3>