-
Notifications
You must be signed in to change notification settings - Fork 72
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
Error installing problemtools on OSX #122
Comments
Using fcntl should be perfectly fine; interactive.cc does not use multithreading so there are no race conditions to worry about. Are you able to make that change locally, check that it works, and send a PR for it? Ideally |
Sure, I'll give that a try in an hour or two. Thanks for the fast response! |
I surrender. Going to just try and hack an OSX build without this dependency for now. |
Now checktestdata fails to compiile - I have bison, but not bisonc++. I'll look into setting that up later. |
Gave up, using Docker. |
Tried to install problemtools on a relatively clean OSX instance. Ran into the following errors:
Install Log
Looks like the issue is in
interactive.cc
: BSD based systems don't havepipe2()
. I'm not really familiar with UNIX programming, but it looks like we're usingpipe2()
to set theFD_CLOEXEC
flag on the pipe. Is there some reason we can't set it withfcntl()
to make this more cross-platform?EDIT: as always, the man page answers my question. Looks like this is a bad race condition :( More digging turned up this rust issue, but it looks like they just gave up on OSX support.
The text was updated successfully, but these errors were encountered: