fortify-headers, branch 0.7

Bump to 0.7

2015-07-24T13:29:06Z

Only crash on overflow for realpath()

2015-07-16T10:45:19Z

Fix stpncpy() check

2015-07-15T16:02:27Z

Do not crash unless the overflow would happen.

Fix confstr() check

2015-07-15T15:05:52Z

Do not crash unless the overflow would actually happen.

Fix wcrtomb() check

2015-07-15T14:55:56Z

This was breaking valid code, example: char c; wcrtomb(&c, L'0', st);

Add extension mark to include_next to silence -pedantic

2015-06-25T09:18:26Z

Signed-off-by: Steven Barth

unistd: fix signed / unsigned comparison in getgroups

2015-06-22T18:05:54Z

Signed-off-by: Steven Barth

Bump to 0.6

2015-06-17T15:37:56Z

Use the inline keyword instead of __inline to avoid breakage

2015-06-04T17:52:50Z

Newer compilers default to GNU11, a C11 dialect. Some software however is unprepared for this or has wrong compatibility checks. What happens is that some software will for compatibility with C89 #define inline before inclusion of a standard header, which is undefined behaviour in C99 and above (C99/C11 7.1.2/4), as inline is a keyword. If any libc headers that are then included via #include_next provide an __inline macro definition (current musl does this if C++ or C99 and above is detected) like the following #define __inline inline this results in any __inline token to be preprocessed away. This breaks use of __builtin_va_arg_pack() in our stdio.h at compile-time as it can only be used in always inlined functions. The function attributes __always_inline__ and __gnu_inline__ themselves require an inline specifier on the function to be applied.

Use namespace-safe macro, param and variable names

2015-06-03T17:55:35Z