Skip to content

Ignore -no_exported_symbols when the debug dylib is used (rdar://152244838) #554

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

Merged
merged 2 commits into from
Jun 5, 2025

Conversation

jonathanpenn
Copy link
Contributor

The stub executor needs to trampoline to the entry point in the debug dylib. But linking with -no_exported_symbols strips it and launching the app fails to find the symbol.

Handles both the LD_EXPORT_SYMBOLS build setting and manual flags added to OTHER_LDFLAGS.

…2244838)

The stub executor needs to trampoline to the entry point in the debug dylib. But linking with `-no_exported_symbols` strips it and launching the app fails to find the symbol.

Handles both the `LD_EXPORT_SYMBOLS` build setting and manual flags added to `OTHER_LDFLAGS`.
@jakepetroules
Copy link
Collaborator

@swift-ci test

@jonathanpenn
Copy link
Contributor Author

Failing linux tests are crashes when running the macro evaluation tests, which are unrelated.

@jonathanpenn jonathanpenn merged commit b133772 into main Jun 5, 2025
20 of 24 checks passed
@jonathanpenn jonathanpenn deleted the dev/jpenn/fix-no-exported-symbols-152244838 branch June 5, 2025 16:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants