cargo: `OUT_DIR` variable not set
Some Travis jobs are not compiling due to OUT_DIR not being present on nightly on my build.rs script. Is this an expected behaviour? how could it be fixed?
Example failure: https://travis-ci.org/SUPERAndroidAnalyzer/super/jobs/181113222#L146
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 27 (24 by maintainers)
Commits related to this issue
- Temporary fix for testing errors The errors were caused by the missing env $OUT_DIR which should be set by cargo, see [here](https://github.com/rust-lang/cargo/issues/3368). — committed to uutils/coreutils by knight42 8 years ago
- Temporary fix for errors in testing The errors were caused by the missing env $OUT_DIR which should be set by cargo. [Related issue](https://github.com/rust-lang/cargo/issues/3368). — committed to uutils/coreutils by knight42 8 years ago
- Fix build failure due to missing environment var Caused by rust-lang/cargo#3368. See https://github.com/rust-lang/cargo/issues/3368#issuecomment-265900350 for more information. — committed to brendanzab/gluon by brendanzab 8 years ago
- Use env::var_os intead of env! in build script The env! method pulls the variable at *compile time* as opposed to runtime. This can cause breakage in scenarios with cross compilation, for example. Cu... — committed to alexcrichton/rust-pinyin by alexcrichton 8 years ago
- Use env::var_os intead of env! in build script The env! method pulls the variable at *compile time* as opposed to runtime. This can cause breakage in scenarios with cross compilation, for example. Cu... — committed to alexcrichton/rust-pinyin by alexcrichton 8 years ago
- Use env::var_os intead of env! in build script The env! method pulls the variable at *compile time* as opposed to runtime. This can cause breakage in scenarios with cross compilation, for example. Cu... — committed to alexcrichton/zip_codes by alexcrichton 8 years ago
- Use env::var intead of env! in build script The env! method pulls the variable at *compile time* as opposed to runtime. This can cause breakage in scenarios with cross compilation, for example. Curre... — committed to alexcrichton/gazetta-bin by alexcrichton 8 years ago
- Fixes broken tests on nightly Caused by https://github.com/rust-lang/cargo/issues/3368. Now the method for determining path for DB tests is exact copy from `cargo`. — committed to vhbit/lmdb-rs by vhbit 7 years ago
I can reproduce this with “cargo install ripgrep” using a cargo built from latest cargo git. Debugging…
Ok we’ve decided to close this as working as intended, but if any projects need help migrating please just let me know!
Can crater be used to find out what on crates.io is broken by this change?