-
Notifications
You must be signed in to change notification settings - Fork 10.5k
build: pass the framework path to the importer #20329
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
Conversation
@swift-ci please test and merge |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
-F flags already get passed through to Clang, so this can't be the right fix.
@jrose-apple - it definitely is getting passed to the linker as a raw |
Pass the framework only to the importer as `-F` on ELF is used for the `DT_FILTER`. Adjust the `DT_RUNPATH` so that the dependent libraries are found.
That sounds like a Clang bug, since Clang is the linker. Right? |
@jrose-apple - fair enough. I don't have a problem with fixing that in clang, but, I think that we should at least do this as a temporary thing. |
That makes sense. If you end up making more changes, then, mind inserting a comment to that effect? Thanks for the explanation! |
@swift-ci please test |
Build failed |
Build failed |
We think this is a Clang issue at heart, but this gets us unblocked.
@swift-ci please clean test macOS platform |
This is to silence the warning when building the lldb test suite.
Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.
Resolves SR-NNNN.