macho: fix logic for parsing dependent dylibs aka re-exports#18677
Merged
macho: fix logic for parsing dependent dylibs aka re-exports#18677
Conversation
Member
Author
|
Oh wow, this did not go as planned for some reason. Lemme re-push the actual changes rebased on master... |
a98d97b to
d62e7bb
Compare
Contributor
|
Hmm, I still seem to get this when trying to cross-compile glfw:
|
Member
Author
I haven't tested this on Nix though. Feel free to submit an issue to that effect. |
This file contains hidden or 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.
Fixes #17130
@slimsag @menduz I would appreciate if you double check this indeed fixes your issue. I did verify locally but want to make sure I didn't have to check out a specific version of
mach-glfwproject or something.@andrewrk a couple of comments regarding having lib and framework search dirs available in
Compilation:I have added dumping those dirs whenEDIT: Turns out I forgot that we already do that for ELF linker. Still, my point stands.--verbose-linkis passed which I find invaluable for debugging any path-related linker issues. That said, I would like to discuss this with you if perhaps we could handle this in the frontend if possible; the point here being having the entire linker line invocation available for dumping when required.