Allow running scheme with custom dynamic libraries on macOS #252
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
anttih
reviewed
Sep 30, 2024
|
I will attempt to update the flake - last time I tried patching the dynamic library loader on linux I didn't have much success, but let's see |
anttih
approved these changes
Oct 4, 2024
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.
Picking up custom paths for loading dynamic libraries through the
DYLD_LIBRARY_PATHis not allowed in the latest macOS version when launching processes in the shell. So we go around this by looking up a custom variable and settingDYLD_LIBRARY_PATHwhen launchingschemeinstead - this works and lets us load dynamic libraries through the envvar instead of having to patch the binary'srpath.