dev-libs/ffcall-1.10-r2 builds ELFs which ask for executable stacks, which causes issues when emerging it's reverse dependencies on a hardened profile. This isn't an issue for version 1.10, so I'd suggest masking version 1.10-r2 for hardened profiles until this can be fixed. ebuild /usr/portage/dev-libs/ffcall/ffcall-1.10-r2.ebuild clean unpack compile scanelf -qeR /var/tmp/portage/dev-libs/ffcall-1.10-r2/work/clisp-2.41 !WX --- --- ./ffcall/avcall/.libs/avcall-x86_64.o RWX --- --- ./ffcall/avcall/.libs/libavcall.so.0.0.0 !WX --- --- ./ffcall/avcall/avcall-x86_64.o !WX --- --- ./ffcall/avcall/avcall.o !WX --- --- ./ffcall/callback/vacall_r/.libs/vacall-x86_64.o RWX --- --- ./ffcall/callback/vacall_r/.libs/libvacall.so.0.0.0 !WX --- --- ./ffcall/callback/vacall_r/vacall-x86_64.o !WX --- --- ./ffcall/callback/vacall_r/vacall.o RWX --- --- ./ffcall/callback/.libs/libcallback.so.0.0.0 !WX --- --- ./ffcall/trampoline/tramp-mips64.old.o.irix6.2 !WX --- --- ./ffcall/vacall/vacall-x86_64.o !WX --- --- ./ffcall/vacall/vacall.o scanelf -lpqe RWX --- --- /usr/lib64/libcallback.so.0.0.0 RWX --- --- /usr/lib64/libavcall.so.0.0.0
According to this post [1] this has been fixed in version 1.13 [1] https://savannah.gnu.org/forum/forum.php?forum_id=8891
=dev-libs/ffcall-2.0 is out there. Closing.