12
167
Fork
You've already forked fnott
32

Fix Build / Notifications on OpenBSD #210

Manually merged
dnkl merged 2 commits from vlkrs/fnott:openbsd into master 2026年05月04日 15:21:48 +02:00
Contributor
Copy link

This applies the trivial patch for UTF-32 support on OpenBSD.
In addition I would like to propose to always define CLOCK_BOOTTIME as CLOCK_MONOTONIC for non-Linux Unices, since epoll-shim does not allow timerfd_create() with clockid values other than CLOCK_MONOTONIC and CLOCK_REALTIME: github.com/jiixyj/epoll-shim@18159584bb/src/timerfd.c (L121)

This applies the trivial patch for UTF-32 support on OpenBSD. In addition I would like to propose to *always* define CLOCK_BOOTTIME as CLOCK_MONOTONIC for non-Linux Unices, since epoll-shim does not allow timerfd_create() with clockid values other than CLOCK_MONOTONIC and CLOCK_REALTIME: https://github.com/jiixyj/epoll-shim/blob/18159584bb3d17e601b9315a7398ace018251bdc/src/timerfd.c#L121
Signed-off-by: vlkrs <vlkrs@noreply.codeberg.org>
fix (notification.c): define CLOCK_BOOTTIME as CLOCK_MONOTONIC
Some checks are pending
ci/woodpecker/pr/woodpecker Pipeline is pending approval
builds.sr.ht/alpine-x64 Job completed
builds.sr.ht/freebsd-x64 Job completed
ci/woodpecker/pull_request_closed/woodpecker Pipeline is pending approval
92a792ba7c 
The BSDs will lean on epoll-shim for timerfd creation, and CLOCK_UPTIME would be rejected.
I witnessed this on OpenBSD, but I am quite certain that anyone using epoll-shim will be hit by the same issue.
18159584bb/src/timerfd.c (L121)
Signed-off-by: vlkrs <vlkrs@noreply.codeberg.org>
dnkl manually merged commit 2d43079ff7 into master 2026年05月04日 15:21:48 +02:00
Sign in to join this conversation.
No reviewers
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
dnkl/fnott!210
Reference in a new issue
dnkl/fnott
No description provided.
Delete branch "vlkrs/fnott:openbsd"

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?