Skip to content
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

Linking an rlib to a dylib may not include native deps #25185

Closed
alexcrichton opened this issue May 7, 2015 · 1 comment
Closed

Linking an rlib to a dylib may not include native deps #25185

alexcrichton opened this issue May 7, 2015 · 1 comment
Labels
A-linkage Area: linking into static, shared libraries and binaries

Comments

@alexcrichton
Copy link
Member

An example showing off this behavior in a gist: https://gist.github.com/anonymous/633c83a89bb6bf479573

This is similar to #15460 which was fixed with the whole-archive option to the linker, and it will likely require the same fix when linking rlibs to a dynamic library to solve this problem as well.

@alexcrichton alexcrichton added the A-linkage Area: linking into static, shared libraries and binaries label May 7, 2015
@alexcrichton
Copy link
Member Author

cc #14344, also very similar.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-linkage Area: linking into static, shared libraries and binaries
Projects
None yet
Development

No branches or pull requests

1 participant