Date: Fri, 10 Mar 2023 19:32:05 +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-wxuCLwNOKX@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 --- Comment #15 from Peter Much <pmc@citylink.dinoex.sub.org> --- (In reply to Ed Maste from comment #14) I've no idea why they're doing it, I just see that they're doing it: =3D=3D=3D> Staging for node16-16.19.0 ... c++ -o /var/local/ports/usr/ports/www/node16/work/node-v16.19.0/out/Release/node -pthread -rdynamic ... ... And yes, certainly, adding a little post-stage task can make it work: post-stage: # USES=3Delfctl does not work here, because of relink during staging ${ELFCTL} -i -e +wxneeded ${STAGEDIR}/usr/local/bin/node Btw, a similar issue is with java/openjdk11, because they compute the build directory dynamically, and I didn't find a way to get that into the .for lo= op in Uses/elfctl (maybe there is one and I'm just not good enough with make -= but it looks difficult). --=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-wxuCLwNOKX>