ci: add macOS build and test job (#407)#409
Merged
thegushi merged 14 commits intoJun 6, 2026
Merged
Conversation
…project#407) The function was implemented and documented but never declared in the public header, causing a build failure on Clang 15+ where implicit function declarations are an error rather than a warning.
Catches Clang-strict build failures (like the missing opendmarc_policy_fetch_fo declaration in issue trusteddomainproject#407) that go undetected on the Linux/GCC job.
libmilter is not a standalone Homebrew formula; it comes from sendmail.
Neither libmilter nor sendmail exist as Homebrew formulae; build from the sendmail source tarball instead.
libmilter.a builds in the current directory, not obj.*/; only mfapi.h and mfdef.h need to be installed, not the internal sendmail.h.
mfapi.h typedef's bool which conflicts with C23 where bool is a keyword.
Same mfapi.h bool conflict as miltertest; gcc defaults to gnu23 on this runner.
…r) and macOS CI
thegushi
added a commit
to thegushi/OpenDMARC
that referenced
this pull request
Jun 6, 2026
…macOS
mlfi_eom() had two large stack allocations that caused a SIGBUS (stack
overflow) crash on macOS ARM64, where threads default to a 512KB stack:
- unsigned char header[MAXHEADER+1]: grew from 1KB to 4KB when MAXHEADER
was bumped from 1024 to 4096 in a prior commit
- struct authres ar: approximately 273KB (MAXARESULTS=32 results, each
with result_property[16][257] and result_value[16][257])
Both are now allocated on the heap via malloc() and freed at the existing
"done:" cleanup label. The goto-done cleanup pattern already present for
header is extended to cover ar; all ar.field accesses are updated to ar->field.
Fixes filter test failures reported on macOS ARM64 (issue trusteddomainproject#409).
This was referenced Jun 6, 2026
thegushi
added a commit
that referenced
this pull request
Jun 6, 2026
…macOS (#410) mlfi_eom() had two large stack allocations that caused a SIGBUS (stack overflow) crash on macOS ARM64, where threads default to a 512KB stack: - unsigned char header[MAXHEADER+1]: grew from 1KB to 4KB when MAXHEADER was bumped from 1024 to 4096 in a prior commit - struct authres ar: approximately 273KB (MAXARESULTS=32 results, each with result_property[16][257] and result_value[16][257]) Both are now allocated on the heap via malloc() and freed at the existing "done:" cleanup label. The goto-done cleanup pattern already present for header is extended to cover ar; all ar.field accesses are updated to ar->field. Fixes filter test failures reported on macOS ARM64 (issue #409).
thegushi
added a commit
to thegushi/OpenDMARC
that referenced
this pull request
Jun 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
build-test-macosjob to CI running onmacos-latest-std=gnu11to avoid a conflict withmfapi.h'stypedef int boolin C23This catches Clang-strict build failures like the missing
opendmarc_policy_fetch_fo()declaration fixed in #408 / issue #407, which went undetected on the Linux/GCC job.Test plan