-
Notifications
You must be signed in to change notification settings - Fork 59
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
Broken when DYLD_LIBRARY_PATH is empty #179
Comments
It looks like this is related to this issue: nasa/europa#181. I don't understand compiletest's internals well, but it seems like it's relying on DYLD_LIBRARY_PATH, which isn't going to work on newer versions of macOS, and the code in question may need to be changed. |
Any ideas/workarounds re: this? Just hit this as well... (Might also be somewhat related: #155) |
The compiletest crate requires lots of flaming hoops, doesn't work if you change features between cargo runs, and currently doesn't work in macOS at all (see Manishearth/compiletest-rs#179). The trybuild crate, on the other hand, seems to work quite well everywhere and gives nice diagnostics. Let's use that instead.
It might fix it once it makes its way to crates.io 😛 |
This might be a good reason for a patch release. |
Yes, sorry about the delay. There's now a version 0.7.0 on crates.io which includes the fix in #235 |
cargo test
in OSX complains about emptyDYLD_LIBRARY_PATH
.because rustc is given two consecutive "-L" "-L":
DYLD_LIBRARY_PATH=dummy cargo test
complains that my lib crate is unresolved. I just migrated to 2018 Edition.extern crate my_lib
didn't work. The snippet in Remove need forextern crate
in 2018 Edition crates #150 didn't work. Cancompiletest-rs
be used in 2018 crates?The text was updated successfully, but these errors were encountered: