mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-09 08:26:00 +02:00
[GH-ISSUE #1631] cmd: darwin build fails with undefined maybeRunAsService/sigHandlerConfigReload #1137
Labels
No labels
ai-generated
android-app
android-app
android-app
🪲 bug
build
build
dependencies
docs
enhancement
enhancement
🔥 HOT
in-progress 🏃
ios
prio:low
prio:low
pull-request
question
🔒 security
server
server
unified-push
web-app
website
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ntfy#1137
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @XYenon on GitHub (Mar 2, 2026).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1631
🐞 Describe the bug
Building the server-enabled CLI on macOS fails due to missing Darwin-specific symbol implementations in the
cmdpackage.cmd/serve.gounconditionally callsmaybeRunAsServiceandsigHandlerConfigReload, but neither is available for Darwin builds, causing compilation to fail.💻 Components impacted
ntfy server (CLI build path), specifically
make cli-darwin-server💡 Screenshots and/or logs
Reproduction command:
Build output:
🔮 Additional context
Root cause appears to be build tags:
cmd/serve.gocalls both functions unconditionally.cmd/serve_windows.goonly builds onwindows && !noserver.cmd/serve_unix.goonly builds onlinux || dragonfly || freebsd || netbsd || openbsd(Darwin missing).This likely regressed when Windows service support was introduced (commit
6d5cc6ae).@aisamu commented on GitHub (Apr 1, 2026):
Hi! I just ran into this.
I've been working around it locally by adding
|| darwinto the build constraint incmd/serve_unix.go:I've been running the server for a couple hours on the default configuration.
Both web and phone notifications triggered as usual, and no errors on server logs.
Nothing indicating breakage so far!
Thanks for this superb project!