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
Watchman on OS X doesn't build with FSEvents #14309
Comments
@pikajude perhaps? Looks like it's either not getting CoreFoundation or CoreFoundation is missing |
We're still using the 10.9 headers for CF which is at v855.17. It looks like it needs to be above 1070. That could be why it's not working. You could try forcing it to use the "CF_new" attribute although that might still be broken. |
@matthewbauer well when I try to use that, it tries to read CF/new.nix but that is not in the tree. I tried to add it but it quickly went over my head. Is there a branch for it somewhere? |
@wmertens You should look at the logs... It's very possible it just never go added. It's going to end up looking like the original with probably some updated patches. I think @copumpkin mainly responsible for most of the SDK stuff in Darwin. |
@matthewbauer @copumpkin seems like we're still at v855.17 of CF. Will this change at some point? I'm having trouble with Elixir's ecto library and the problem is probably the same. |
Recreated using this derivation breaks on 10.12.6 (16G29): environment setup steps
actual reproduction
After the touch command, you should see something like the following in your terminal:
You have to run |
So the fundamental issue here is that the public CF projects don't define |
created the following: https://bugs.swift.org/browse/SR-6136 |
Any update here? |
Watchman uses kqueue instead of FSEvents, which makes it basically unusable. This can be verified by looking at the log which starts with
Using watcher mechanism kqueue
.I traced it down to CoreServices not being provided as a build input, but when I try to do that I get these build errors:
To build, I use this
nixpkgs/config.nix
:and this
watchman.nix
:/cc @copumpkin or @shlevy any ideas on how to fix this build? @cstrahan I presume you're not using Darwin? Any others that may know?
The text was updated successfully, but these errors were encountered: