diff options
| author | bors <bors@rust-lang.org> | 2014-05-20 19:16:15 -0700 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2014-05-20 19:16:15 -0700 |
| commit | f30382d624d4a523262df05234b1c20b7de4ac0c (patch) | |
| tree | df2ca8b7d2201e16d1fa23c7b6a6c672eb240a61 /src/rustllvm/ExecutionEngineWrapper.cpp | |
| parent | e546452727379f701f2104eb826141a29d4b39fd (diff) | |
| parent | ae67b74ec826cfc00467b9d4355beb307315d08b (diff) | |
| download | rust-f30382d624d4a523262df05234b1c20b7de4ac0c.tar.gz rust-f30382d624d4a523262df05234b1c20b7de4ac0c.zip | |
auto merge of #13823 : pnkfelix/rust/fsk-fix-13805, r=alexcrichton
Make configure script respect (and save) values for `CC`, `CXX`, `CFLAGS` etc. I mostly tried to remain backwards compatible with old invocations of the `configure` script; if you do not want to use `CC` et al., you should not have to; you can keep using `--enable-clang` and/or `--enable-ccache`. The overall intention is to capture the following precedences for guessing the C compiler: 1. Value of `CC` at `make` invocation time. 2. Value of `CC` at `configure` invocation time. 3. Compiler inferred at configure invocation time (`gcc` or `clang`). The strategy is to check (at `configure` time) if each of the environment variables is set, and if so, save its value in a corresponding `CFG_` variable (e.g. `CFG_CC`). The `configure` script also does not attempt to infer the compiler if `CC` is set; but if `--enable-clang` was passed, then it *does* still attempt to validate that the clang version is compatible. Then, in the makefiles, if `CC` is not set but `CFG_CC` is, then we use the `CFG_CC` setting as `CC`. Fix #13805.
Diffstat (limited to 'src/rustllvm/ExecutionEngineWrapper.cpp')
0 files changed, 0 insertions, 0 deletions
