FUSE 3.12 support #15
Merged
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
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.
This adds support for FUSE 3.12, which introduced some incompatibilities. In order to support both 3.12 as well as older libfuse .so versions, you would usually rely on versioned ABI via
dlvsym. However, this is not usually supported in Panama, so we need some if/else switching depending onfuse_version().Related discussions:
SymbolLookup, which supports versioned symbolsThe custom SymbolLookup might be the better approach for libfuse, however it requires adjusted jextracted code, which is terrible for future re-jextract-ions. We should reevaluate this approach, if jextract ever allows using a custom SymbolLookup, though. Or if we ever decide to drop jextract and maintain method handles and structs by hand.