Created attachment 129141 [details]
Patch, adding the missing buildreqs

This is failing with something else now:

gcc -g -fomit-frame-pointer -O2 -Wall -I. -DINTERFACE_VERSION=3
-D_LARGEFILE64_SOURCE -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic
-fasynchronous-unwind-tables -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
  -c tux.c
tux.c:51: error: expected declaration specifiers or '...' before 'tux'
tux.c:51: error: expected declaration specifiers or '...' before 'action'
tux.c:51: error: expected declaration specifiers or '...' before 'req'
tux.c:55: warning: return type defaults to 'int'
tux.c: In function '_syscall2':
tux.c:74: error: storage class specified for parameter 'nr_threads'
tux.c:75: error: storage class specified for parameter 'shared_buf'
tux.c:76: error: storage class specified for parameter 'shared_idx'
tux.c:76: error: parameter 'shared_idx' is initialized
tux.c:78: error: storage class specified for parameter 'max_module_idx'
tux.c:78: error: parameter 'max_module_idx' is initialized
tux.c:79: error: storage class specified for parameter 'handle_events_array'

and on and on...

glibc seems to have stopped defining _syscall2 in unistd.h

Should tux carry a private declaration of this macro, or is this likely to come
back in a glibc update?

glibc never defined these, it is glibc-kernheaders that used to define them,
originally to helplessly broken macros, later on to syscall function invocation.
That's what apps should be actually using, not sure why glibc-kernheaders no
longer defines that in <linux/unistd.h>.

glibc-kernheaders is not intended for use by normal userspace programs.
Applications should use the syscall() function which glibc provides.

I think I've fixed this up. It's stalled on building for the s390 though.
Other archs have now built successfully.

fixed.