From: Nadav Har'El <[email protected]> Committer: Nadav Har'El <[email protected]> Branch: master
Avoid implicit int When I learned C, some 40 years ago, it was common to drop the keyword "int" in various places in function declaration, assuming "int" was the default. This practice faded over the years, but gcc still accept some cases of "implicit int" for many years, until gcc 14.1.1 started to crack down on them. This patch fixes one case of implied "int" that gcc no longer accepts. Signed-off-by: Nadav Har'El <[email protected]> --- diff --git a/include/api/string.h b/include/api/string.h --- a/include/api/string.h +++ b/include/api/string.h @@ -59,7 +59,7 @@ char *strerror (int); char *strtok_r (char *__restrict, const char *__restrict, char **__restrict); #ifndef _GNU_SOURCE int __xpg_strerror_r (int, char *, size_t); -static inline strerror_r(int __errnum, char* __buf, size_t __bufsize) +static inline int strerror_r(int __errnum, char* __buf, size_t __bufsize) { return __xpg_strerror_r(__errnum, __buf, __bufsize); } -- You received this message because you are subscribed to the Google Groups "OSv Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/osv-dev/000000000000e62165061bf46924%40google.com.
