use -Werror=implicit-function-declaration for function detection the previous -Werror triggers too easily: on NixOS for example the FORTIFY_SOURCE #warning about a missing optimization level breaks all the checks when using -O0 (which is the default for non-release builds).

fix landlock test include stddef.h for size_t

remove dead code

update mac CI target to sonoma

fix `log access path' with chroot We should open the log file inside the chroot; missed in 4acf495f41d2c26136e99072293ca8b9bff91dc0. See https://github.com/omar-polo/gmid/issues/24

revert 9f1cce3d0e53209180eabbcd48878c1e989101e7 we actually should open the log file in the chroot, the bug is in the code.

fix log access doc: path is not relative to the chroot Reported by Colin Henein, thanks! See https://github.com/omar-polo/gmid/issues/24

add a note regarding the usage of the bundled libtls See https://codeberg.org/op/gmid/issues/2

sync changelog

contrib/vim: fix indent

rename the @common_opt macro back to @common now common is no longer a reserved keyword

turn log styles into strings from yacc point of view having styles as reserved keywords means that variables / macros can't be called `common', `condensed', etc... which is not great and not obvious either. Instead, let's keep the log styles as strings and match on them. This also allows to have a slightly better error message in case of a typo. See: https://codeberg.org/op/gmid/issues/1

remove stray space

tweak and update freebsd task

rework the grammar so that ; is accepted after variables and options See Codeberg issue #1.