Re: On the remaining syscall(2) or __syscall(2) use in ports

Christian Weisgerber <naddy@mips.inka.de> wrote:

e> Theo Buehler:
>
> > devel/p5-IO-AIO
> > (?) strange mix of perl + m4
>
> The m4 part are just autoconf macros that are included by the
> top-level configure.ac. I looked over this and the syscalls are
> Linux-specific and behind #ifdef guards. On OpenBSD this is
> already short-ciruited to syscall(-1, ...). There is also a
> configure check for the presence of syscall() and
>
> #if HAVE_SYSCALL
> #include <sys/syscall.h>
> #else
> # define syscall(nr,...) (errno = ENOSYS, -1)
>