Skip to content

Adds a more comprehensive check for fdatasync #42

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

Merged
merged 1 commit into from
Mar 9, 2015
Merged

Adds a more comprehensive check for fdatasync #42

merged 1 commit into from
Mar 9, 2015

Conversation

argiopetech
Copy link
Contributor

Some versions of OS X have fdatasync in the headers but don't include implementations in the standard library. This leads to a compile failure in configure.ac when using AC_CHECK_FUNCS.

This change explicitly attempts to compile a file containing a call to fdatasync and properly sets the AC_CHECK_FUNCS flags depending on the result of compilation.

May fix #37.

Some versions of OS X have fdatasync in the headers but don't include implementations in the standard library. This leads to a compile failure in configure.ac when using AC_CHECK_FUNCS.

This change explicitly attempts to compile a file containing a call to fdatasync and properly sets the AC_CHECK_FUNCS flags depending on the result of compilation.
argiopetech added a commit that referenced this pull request Mar 9, 2015
Adds a more comprehensive check for fdatasync
@argiopetech argiopetech merged commit 94d8824 into haskell:master Mar 9, 2015
hvr added a commit that referenced this pull request Dec 16, 2015
This attempts a simpler and hopefully more robust test for `fdatasync(2)`

See 94d8824 / #42 for the previous attempt.

This hopefully addresses #52 in a better way than #53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Problem with fdatasync when cross compiling to aarch64 on Mac OS X
3 participants