-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OSX/BSD/Solaris support blockers #94
Comments
There have been discussions of making Hindsight cross platform (including Windows), ranging from C11 threading/wrapper to a Rust implementation. It is simply a matter of time and energy which we have decided to devote elsewhere. This next quarter will focus on integration testing (mainly for the various Mozilla Heka sandboxes but it will also provide good coverage of Hindsight itself; reducing a lot of manual test effort). OSX/BSD/Solaris are a quicker wins but wouldn't necessarily help towards the longer term cross platform goal, it would also add to the support and test burden in the short term. Since we don't use those platforms in our infrastructure an automated build and test environment would be required for each as part of those changes. As for the clock_get_time code, the portable solution in the lua_sandbox can be used. |
inotify should be added to this list Related: #72 |
inotify might solved by libinotify-kqueue |
The pthread_timedjoin_np() is a FreeBSD extension which first appeared in FreeBSD 6.1. |
@beorn-: Is the document that I linked to above incorrect/out of date?
|
I think so this is taken from a freebsd man
|
Kudos on Hindsight!
Here is a list of known blockers preventing hindsight from running on various systems:
Known issues:
pthread_timedjoin_np
is not available on non-glib operating systems sourceclock_get_time
is not available on OSX until 10.12 (Sierra) this issue provides an outline of how the hack can be conditionally applied for maximum compatibility.sem_init
is deprecated andsem_timedwait
is unavailable (possible solution)inotify
(possible solution from @zloidemon)@trink: Perhaps contributors can champion these issues with a little guidance on what solutions you'd be comfortable to accept upstream with a PR?
Thank you for your hard work,
Jeff
The text was updated successfully, but these errors were encountered: