Based on nm output generated by sthen back in November (which doesn't capture Go a.k.a. the elephant in the room) the following ports used syscall(2) or __syscall(2).
It would be nice if the maintainers (or someone who cares) could take a closer look and send diffs to replace syscall(2) use by direct calls to the appropriate syscall (if possible). Here are the remaining known offenders (excluding >100 Go ports) devel/boost,-main (brad, rsadowski) futex-wrappers in boost/atomic/detail/futex.cpp + maybe more? devel/openmpi (martin) memory_patcher_syscall() wrapper around various syscalls devel/tbb (?) ends up using syscall(2) in generated source devel/p5-IO-AIO (?) strange mix of perl + m4 lang/ruby/*,-main (jeremy) Ruby has a rarely used syscall wrapper. Ruby is usually smart, so maybe the build system will disable this when syscall(2) goes away. pending fixes ------------- devel/droplet patch sent to rsadowski multimedia/libv4l kn has a tentative diff fixed ----- devel/abseil-cpp devel/glog devel/libusb1 graphics/blender devel/jdk/1.8 lang/mono lang/tcc
