Re: SH build problem with fanotify_mark

[Roland McGrath <roland at hack dot frob dot com>]

> I've forgotten to say that with some recent change on git tree
> my SH build was broken like as
> 
> /exp/ldroot/dodes/xsh-libc-intest/misc/stub-syscalls.c:3:22: warning: ISO C99 requires whitespace after the macro name [enabled by default]
> /exp/ldroot/dodes/xsh-libc-intest/misc/stub-syscalls.c:14:21: warning: extra tokens at end of #undef directive [enabled by default]
> /exp/ldroot/dodes/xsh-libc-intest/misc/stub-syscalls.c:32:1: error: stray '@' in program
> /exp/ldroot/dodes/xsh-libc-intest/misc/stub-syscalls.c:32:1: error: stray '@' in program
> /exp/ldroot/dodes/xsh-libc-intest/misc/stub-syscalls.c:32:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'GLIBC_2'
> /exp/ldroot/dodes/xsh-libc-intest/misc/stub-syscalls.c:32:64: error: invalid suffix "_GLIBC_2.16" on floating constant
> make[2]: *** [/exp/ldroot/dodes/xsh-libc-intest/misc/stub-syscalls.o] Error 1

That's without the roland/getrlimit change?  Show us any unix-stub-syscalls
lines in your sysd-syscalls file, and the stub-syscalls.c file.  Aside from
my branch, make-syscalls.sh hasn't changed in a few months.  Perhaps it was
always broken for versioned cases?  The sysdeps/unix/Makefile rule that
generates stub-syscalls.c handles them, but I don't know how much it's
actually exercised.  Or maybe there's something wrong with your shell?

Anyway, I'd forgotten entirely about stub-syscalls.c and now I see my
branch ought to change it to match the change to how the real syscalls
are generated after my make-syscalls.sh changes.  I'll take care of that
on Monday.


Thanks,
Roland