-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Fix Darwin build #1093
Fix Darwin build #1093
Conversation
No idea if tests are expected to pass, but I'm 👍 on this or just removing the define altogether. Anything in the commit logs indicate why it's there? |
It looks like it was added by copumpkin@77d2726, possibly to support large files? Not sure if it's still relevant. |
I'd just nuke it. |
f488052
to
15085e4
Compare
Okay, I nuked it. Here are the failures (it claims there are 9 this time, but I see more
I almost feel like the test is using the wrong Nix on my system, based on those test failures? |
Yeah that's really strange... |
So yeah, I sandwiched a
So something is wonky with |
Okay, partial PEBKAC. I wasn't running After running
|
Done slightly differently from #1093.
I've just pushed a fix for that (af3db85). |
Oh thanks. I assumed you were trying to avoid using |
Oh sorry, misread your commit. You pushed a commit fixing the broken tests, and separately pushed a commit that fixed the broken build. Thanks! |
Build works and all tests now pass on Darwin on master! |
This should fix #1091, #1092, and #1013.
make installcheck
shows that 10 tests failed, so this is effectively untested and I don't know whether that's expected. I don't really have a last known good state to check against.@edolstra @shlevy can you give some guidance on how to test this properly? Are all tests expected to pass on Darwin?
Also, I'd prefer to delete the
_XOPEN_SOURCE
altogether if possible, but if we keep it, it should be 700.