> I ran into a similar backtrace with Taisei [0]. Most seemingly it needs > to USE_NOBTCFI=Yes as our Boost sits at 1.80.0, while CET was introduced > in boost::context at 1.81.0 and updating Boost is not an option at this > point. > > I successfully tested it with USE_NOBTCFI. > > [0]: https://github.com/taisei-project/koishi/issues/6#issue-1888944976 >
Committed this slightly tweaked diff, thanks. REVISION bump is needed since the package changed. Maybe USE_NOBTCFI-amd64 would be enough, but I think at this point in the cycle it's better to play it safe. Index: Makefile =================================================================== RCS file: /cvs/ports/net/powerdns_recursor/Makefile,v retrieving revision 1.45 diff -u -p -r1.45 Makefile --- Makefile 27 Sep 2023 14:18:29 -0000 1.45 +++ Makefile 30 Sep 2023 10:38:58 -0000 @@ -4,6 +4,7 @@ V= 4.9.1 DISTNAME= pdns-recursor-${V} EXTRACT_SUFX = .tar.bz2 PKGNAME= powerdns-recursor-${V} +REVISION= 0 CATEGORIES= net @@ -11,6 +12,9 @@ HOMEPAGE= https://www.powerdns.com/ # GPLv2 only, OpenSSL exemption PERMIT_PACKAGE= Yes + +# SIGILL on startup because of boost::context. Needed until boost >= 1.81. +USE_NOBTCFI= Yes WANTLIB+= ${COMPILER_LIBCXX} boost_context-mt boost_filesystem-mt WANTLIB+= boost_system-mt boost_thread-mt c crypto curl fstrm m