fortify-headers/tests, branch master

Use shared COMMON_FLAGS in tests

2026-04-12T22:05:57Z

Fixes CXXFLAGS missing -I../include/ and avoids similar issues to happen in the future

Ensure in tests/common.h that fortify-headers.h was included

2026-04-12T22:05:57Z

Exposes bug in c++ compile test which do not include fortify-headers

Make do even if PATH_MAX isn't defined

2026-04-01T18:37:02Z

As explained in `man realpath(3)`: > The POSIX.1-2001 standard version of this function is broken by design, > since it is impossible to determine a suitable size for the output > buffer, resolved_path. According to POSIX.1-2001 a buffer of size PATH_MAX > suffices, but PATH_MAX need not be a defined constant, and may have to be > obtained using pathconf(3). And asking pathconf(3) does not really help, > since, on the one hand POSIX warns that the result of pathconf(3) may be huge > and unsuitable for mallocing memory, and on the other hand pathconf(3) may > return -1 to signify that PATH_MAX is not bounded. The re‐ solved_path > == NULL feature, not standardized in POSIX.1-2001, but standardized in > POSIX.1-2008, allows this design problem to be avoided. So we can either not compile, or be pragmatic, and define PATH_MAX to a sane value, like 4096, which is the one used on Linux and some/most BSD. This commit also adds two tests to ensure that things aren't catastrophically broken by this change.

Add some compilers flags to the C++ testsuite

2026-03-13T00:11:35Z

Notably -Wno-fortify-source, to prevent clang from using its own fortify implementation. Co-Authored-By: Sertonix

Fixes compilation with clang and -D_FORTIFY_SOURCE=2

2026-03-13T00:11:26Z

This commit fixes the typo pass_object_size__ for pass_object_size. It also adds tests in the CI to prevent this from happening again. Ref https://clang.llvm.org/docs/AttributeReference.html#pass-object-size-pass-dynamic-object-size Co-Authored-By: Sertonix

Add a testsuite

2025-11-11T13:09:16Z

Co-Authored-By: q66