Linking issues using Cargo-built libraries from non-cargo projects.

[ghost]

This repository tells all: https://github.com/Kingsquee/unfound

[ghost]

My suspicion is it relates to cargo's opinionated compilation of dependencies (afaik, cargo doesn't just let me set a dependency's crate type), but the error cases are still very strange.

[ghost]

rust-lang/rust#18807 seems similar, especially with this 'solution'

[alexcrichton]

It looks like you're running into rust-lang/rust#14344 because the rlib foo is being linked into the dylib state, but that bug means it's not actually being included. Later on when process depends on foo as well (but thinks it gets it through state), the assumption is incorrect and a link error happens.

I'm going to close this in favor of that issue, though.