Am 05.11.2011 16:37, schrieb Johannes Sixt: > Commit f696543d (Add strtoimax() compatibility function) introduced an > implementation of the function, but forgot to add a declaration. On second thought, I'm puzzled: Without this patch and without noticing the warning that strtoimax() was not declared, I had built with NO_STRTOUMAX on MinGW before, and the build succeeded. This means that even though MinGW's headers are not C99, we must have pulled in function strtoimax() from somewhere. I'll investigate later this weekend. Anyway, this patch does not just add a declaration for the function, but also redirects strtoimax to gitstrtoimax, which is a bit more than the commit message claims. Without this patch, topic na/strtoimax should not build on a non-C99 environment. Can you verify this claim? -- Hannes > > Signed-off-by: Johannes Sixt <j6t@xxxxxxxx> > --- > git-compat-util.h | 2 ++ > 1 files changed, 2 insertions(+), 0 deletions(-) > > diff --git a/git-compat-util.h b/git-compat-util.h > index feb6f8e..4efef46 100644 > --- a/git-compat-util.h > +++ b/git-compat-util.h > @@ -354,6 +354,8 @@ extern size_t gitstrlcpy(char *, const char *, size_t); > #ifdef NO_STRTOUMAX > #define strtoumax gitstrtoumax > extern uintmax_t gitstrtoumax(const char *, char **, int); > +#define strtoimax gitstrtoimax > +extern intmax_t gitstrtoimax(const char *, char **, int); > #endif > > #ifdef NO_STRTOK_R -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html