On Tue, May 29, 2018 at 11:58 AM, Manu Raster <manu.ras...@gmail.com> wrote: > Strlcpy works fine with Linux and gcc, too. It's probably just a clang > or apple bug.
I don't believe it's a clang bug, but just that the strlcpy definition clashes with the macro which is imported via <string.h>. (OS X defines both a C function and a macro by the same name which wraps it, at least at FORTIFY_SOURCE levels above 0.) I notice that iic does #undef strlcpy before the prototype definition, but strlcpy.c does not. Adding that allows ii to build for me.
