about summary refs log tree commit diff
path: root/src/rustllvm/RustWrapper.cpp
diff options
context:
space:
mode:
authorAlex Crichton <alex@alexcrichton.com>2014-07-30 07:44:20 -0700
committerAlex Crichton <alex@alexcrichton.com>2014-08-04 11:02:26 -0700
commit1ae1461fbf59db8db5dd2fe11bbe22c6adeb1aed (patch)
treee79679953309797f1b392fda875b33031bd4ee81 /src/rustllvm/RustWrapper.cpp
parent31590bd34900403a18079bf4623cd35f9da0c100 (diff)
downloadrust-1ae1461fbf59db8db5dd2fe11bbe22c6adeb1aed.tar.gz
rust-1ae1461fbf59db8db5dd2fe11bbe22c6adeb1aed.zip
rustc: Link entire archives of native libraries
As discovered in #15460, a particular #[link(kind = "static", ...)] line is not
actually guaranteed to link the library at all. The reason for this is that if
the external library doesn't have any referenced symbols in the object generated
by rustc, the entire library is dropped by the linker.

For dynamic native libraries, this is solved by passing -lfoo for all downstream
compilations unconditionally. For static libraries in rlibs this is solved
because the entire archive is bundled in the rlib. The only situation in which
this was a problem was when a static native library was linked to a rust dynamic
library.

This commit brings the behavior of dylibs in line with rlibs by passing the
--whole-archive flag to the linker when linking native libraries. On OSX, this
uses the -force_load flag. This flag ensures that the entire archive is
considered candidate for being linked into the final dynamic library.

This is a breaking change because if any static library is included twice in the
same compilation unit then the linker will start emitting errors about duplicate
definitions now. The fix for this would involve only statically linking to a
library once.

Closes #15460
[breaking-change]
Diffstat (limited to 'src/rustllvm/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions