summary refs log tree commit diff
path: root/src/bootstrap
AgeCommit message (Collapse)AuthorLines
2018-12-05build the edition guideSteve Klabnik-1/+2
and update it so that links are correct
2018-11-30Add the edition guide to doc.rust-lang.orgSteve Klabnik-0/+1
2018-11-22Forward rust version number to toolsOliver Scherer-0/+2
Clippy uses it to identify the correct documentation to point to
2018-11-22fix rustbuild to build all the booksSteve Klabnik-11/+15
2018-11-10rustbuild: use configured linker to build boostrapMarc-Antoine Perennou-0/+3
Signed-off-by: Marc-Antoine Perennou <Marc-Antoine@Perennou.com>
2018-11-07Move a few more tests into the appveyor-subset-2.kennytm-1/+6
This should allow the timings be more balanced.
2018-11-07Ensure --exclude is checked against PathSet::Suitekennytm-2/+37
Fix the recent spurious 3 hour timeouts.
2018-10-31rustbuild: fix remap-debuginfo when building a releaseMarc-Antoine Perennou-1/+1
Fallback to the release number as we can't get the git commit sha as we're not in a git repository. Fixes #55341 Signed-off-by: Marc-Antoine Perennou <Marc-Antoine@Perennou.com>
2018-10-29Remove redundant cloneShotaro Yamada-3/+3
2018-10-23fix typos in various placesMatthias Krüger-1/+1
2018-10-21Remove the parse-fail test suiteVadim Petrochenkov-7/+0
2018-10-20Update Cargo, build curl/OpenSSL statically via featuresAlex Crichton-234/+35
In addition to to updating Cargo's submodule and Cargo's dependencies, this also updates Cargo's build to build OpenSSL statically into Cargo as well as libcurl unconditionally. This removes OpenSSL build logic from the bootstrap code, and otherwise requests that even on OSX we build curl statically.
2018-10-20Auto merge of #55014 - ljedrz:lazyboye_unwraps, r=matthewjasperbors-2/+2
Prefer unwrap_or_else to unwrap_or in case of function calls/allocations The contents of `unwrap_or` are evaluated eagerly, so it's not a good pick in case of function calls and allocations. This PR also changes a few `unwrap_or`s with `unwrap_or_default`. An added bonus is that in some cases this change also reveals if the object it's called on is an `Option` or a `Result` (based on whether the closure takes an argument).
2018-10-19Derives often have very strict boundsOliver Scherer-1/+9
2018-10-19Prefer `Default::default` over `FxHash*::default` in struct constructorsOliver Scherer-16/+4
2018-10-19Prefer unwrap_or_else to unwrap_or in case of function calls/allocationsljedrz-2/+2
2018-10-18Rollup merge of #55031 - nikic:verify_llvm_ir, r=Mark-Simulacrumkennytm-8/+3
Improve verify_llvm_ir config option LLVM IR verification has been disabled by default in #51230. However, the implementation doesn't quite match what was discussed in the discussion. This patch implements two changes: * Make `verify_llvm_ir` influence the behavior of the compiled rustc binary, rather than just the rustc build system. That is, if `verify_llvm_ir=true`, even manual invocations of the built rustc will verify LLVM IR. * Enable verification of LLVM IR in CI, for non-deploy and deploy-alt builds. This is similar to how LLVM assertions are handled.
2018-10-18Rollup merge of #54964 - tromey:run-both-gdb-and-lldb-tests, r=nikomatsakiskennytm-14/+6
Run both lldb and gdb tests Currently lldb tests are run only on macOS, and gdb tests are only run elsewhere. This patch changes this to run tests depending on what is available. One test is changed, as it was previously marked as failing on macOS, whereas really it is a generic failure with lldb. Closes #54721
2018-10-14Auto merge of #55051 - matthiaskrgr:dist_msg, r=Mark-Simulacrumbors-0/+3
boostrap: dist: if a file cannot be installed because it does not exist, print its name in the error message.
2018-10-13boostrap: dist: if a file cannot be installed because it does not exist, ↵Matthias Krüger-0/+3
print its name in the error message.
2018-10-13bootstrap: update clippy license locations which changed due to relicensing.Matthias Krüger-2/+4
2018-10-13Improve verify_llvm_ir config optionNikita Popov-8/+3
* Make it influence the behavior of the compiled rustc, rather than just the rustc build system. That is, if verify_llvm_ir=true, even manual invocations of the built rustc will verify LLVM IR. * Enable verification of LLVM IR in CI, for non-deploy and deploy-alt builds. This is similar to how LLVM assertions are handled.
2018-10-12Rollup merge of #54811 - ↵kennytm-1/+3
pnkfelix:issue-24840-separate-bootstrap-default-for-optimize-from-debug-setting, r=nikomatsakis During rustc bootstrap, make default for `optimize` independent of `debug` It may have taken me three and a half years, but I'm following through on my ["threat"](https://github.com/rust-lang/rust/issues/24840#issuecomment-97911700) Fix #24840
2018-10-10Run both lldb and gdb testsTom Tromey-14/+6
Currently lldb tests are run only on macOS, and gdb tests are only run elsewhere. This patch changes this to run tests depending on what is available. One test is changed, as it was previously marked as failing on macOS, whereas really it is a generic failure with lldb. Closes #54721
2018-10-10Auto merge of #54764 - tromey:test-rust-lldb, r=alexcrichtonbors-23/+27
Run debuginfo tests against rust-enabled lldb, when possible If the rust-enabled lldb was built, then use it when running the debuginfo tests. Updating the lldb submodule was necessary as this needed a way to differentiate the rust-enabled lldb, so I added a line to the --version output. This adds compiletest commands to differentiate between the rust-enabled and non-rust-enabled lldb, as is already done for gdb. A new "rust-lldb" header directive is also added, but not used in this patch; I plan to use it in #54004. This updates all the tests.
2018-10-08Run debuginfo tests against rust-enabled lldb, when possibleTom Tromey-23/+27
If the rust-enabled lldb was built, then use it when running the debuginfo tests. Updating the lldb submodule was necessary as this needed a way to differentiate the rust-enabled lldb, so I added a line to the --version output. This adds compiletest commands to differentiate between the rust-enabled and non-rust-enabled lldb, as is already done for gdb. A new "rust-lldb" header directive is also added, but not used in this patch; I plan to use it in #54004. This updates all the tests.
2018-10-04Fix #24840: make default for `optimize` independent of `debug` setting in ↵Felix S. Klock II-1/+3
`Cargo.toml`.
2018-10-04Auto merge of #54638 - christianpoveda:master, r=kennytmbors-5/+18
Add checking for tool distribution in Tier 1 This fixes https://github.com/rust-lang/rust/issues/54483 r? @kennytm
2018-10-01Fix conditions to allow missing tools in CIChristian Poveda-1/+3
2018-10-01Rollup merge of #54708 - collin5:b49475, r=Mark-Simulacrumkennytm-0/+5
Make ./x.py help <cmd> invoke ./x.py <cmd> -h on its own Fixes #49475 r? @Mark-Simulacrum
2018-10-01Rollup merge of #54681 - alexcrichton:san-names, r=kennytmkennytm-1/+1
Rename sanitizer runtime libraries on OSX Currently we ship sanitizer libraries as they're built, but these names unfortunately conflict with the names of the sanitizer libraries installed on the system. If a crate, for example, links in C code that wants to use the system sanitizer and the Rust code doesn't use sanitizers at all, then using `cargo` may accidentally pull in the Rust-installed sanitizer library due to a conflict in names. This change is intended to be entirely transparent for Rust users of sanitizers, it should only hopefully improve our story with other users! Closes #54134
2018-10-01allow use of ./x.py help <cmd> ...Collins Abitekaniza-0/+5
2018-09-29Rename sanitizer runtime libraries on OSXAlex Crichton-1/+1
Currently we ship sanitizer libraries as they're built, but these names unfortunately conflict with the names of the sanitizer libraries installed on the system. If a crate, for example, links in C code that wants to use the system sanitizer and the Rust code doesn't use sanitizers at all, then using `cargo` may accidentally pull in the Rust-installed sanitizer library due to a conflict in names. This change is intended to be entirely transparent for Rust users of sanitizers, it should only hopefully improve our story with other users! Closes #54134
2018-09-28Add enable-missing-tools optionChristian Poveda-5/+16
2018-09-27Bump to 1.31.0 and bootstrap from 1.30 betaJosh Stone-1/+1
2018-09-25Improvements to finding LLVM's FileCheckTom Tromey-2/+33
This patch adds a few improvements to how the build system finds LLVM's FileCheck program. * On Fedora, the system LLVM installs FileCheck in the "llvm" subdirectory of the LLVM libdir. This patch teaches the build system to look there. * This adds a configure option to specify which llvm-config executable to use. This is handy on systems that can parallel install multiple versions of LLVM; for example I can now: ./configure --llvm-config=/bin/llvm-config-5.0-64 ... to build against LLVM 5, rather than whatever the default llvm-config might be. * Finally, this adds a configure- and config.toml- option to set the path to FileCheck. This is handy when building against an LLVM where FileCheck was not installed. This happens on compatibility installs of LLVM on Fedora.
2018-09-22Rollup merge of #54323 - Keruspe:rustc-color, r=Mark-SimulacrumPietro Albini-42/+1
rustbuild: drop color handling Let cargo handle that for us Fixes #54322 Needs a beta backport
2018-09-21Run the newly `ui`-ified run-pass tests under `compare-mode=nll` as well.Felix S. Klock II-2/+3
Fix #53764.
2018-09-18rustbuild: drop color handlingMarc-Antoine Perennou-42/+1
Let cargo handle that for us Signed-off-by: Marc-Antoine Perennou <Marc-Antoine@Perennou.com>
2018-09-17Auto merge of #52036 - collin5:b50509-2, r=collin5bors-109/+90
Clean up dependency tracking in Rustbuild [2/2] Make `clear_if_dirty` calls in `Builder::cargo` with stamp dependencies for the given Mode. Continuation of #50904 Ref issue #50509 r? @Mark-Simulacrum
2018-09-17refactor Builder::cargo, clean deps for cmd!=testCollins Abitekaniza-6/+2
2018-09-14Rollup merge of #53829 - alexcrichton:release-debuginfo, r=michaelwoeristerkennytm-12/+54
Add rustc SHA to released DWARF debuginfo This commit updates the debuginfo that is encoded in all of our released artifacts by default. Currently it has paths like `/checkout/src/...` but these are a little inconsistent and have changed over time. This commit instead attempts to actually define the file paths in our debuginfo to be consistent between releases. All debuginfo paths are now intended to be `/rustc/$sha` where `$sha` is the git sha of the released compiler. Sub-paths are all paths into the git repo at that `$sha`.
2018-09-12Add check build dependenciesMark Rousskov-6/+6
2018-09-12Do not print checking messages in dry run modeMark Rousskov-3/+3
2018-09-12remove struct CleanToolsCollins Abitekaniza-53/+22
2018-09-12nit: rearrange and make match exhaustiveCollins Abitekaniza-5/+8
also indicate difference between out_dir and my_out
2018-09-12clear_if_dirty with self.rustc(compiler) for Mode::RustcCollins Abitekaniza-0/+1
2018-09-12use stage 1 compiler only for stampsCollins Abitekaniza-8/+8
2018-09-12clear_if_dirty in Builder::cargo with passed modeCollins Abitekaniza-52/+64
2018-09-12Rollup merge of #54073 - behnam:docs-1, r=frewsxcvkennytm-9/+9
docs: Use dollar sign for all bash prompts Making it consistent across the board, as most of them already use `$`. Also split one continues bash run into two, to make it easier see different runs: one with warning and another with error.