Fix FFI undefined symbol stat64 by falling back to syscall #62
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi @Matthew-Allen, thanks for this pull request. I was having issues reproducing this issue, so it is nice to have fix for this. This will be merged in the next release. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #37
FFI fails to create a binding for stat64 (and other stat functions such as stat, lstat, etc) on systems where macros are heavily used in the definition of said functions. This fix builds off of the workaround by @pirogronian, but instead of falling back to LOVE filesystem utilities, uses syscalls to produce equivalent functionality to stat64.