about summary refs log tree commit diff
path: root/src/rt/rust_kernel.cpp
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2013-07-10 01:10:29 -0700
committerbors <bors@rust-lang.org>2013-07-10 01:10:29 -0700
commit8a7b636649db7601bbef90c525eea2a457ba3a8c (patch)
treedb2ed719f8e59cb89c89839f5054365665696a59 /src/rt/rust_kernel.cpp
parentb5e9194836cab666163cf97cfbea6a323edad882 (diff)
parentace49442a6aef323d42700da169ac3de32d64c2d (diff)
downloadrust-8a7b636649db7601bbef90c525eea2a457ba3a8c.tar.gz
rust-8a7b636649db7601bbef90c525eea2a457ba3a8c.zip
auto merge of #7637 : pnkfelix/rust/fsk-guard-against-stale-libraries-issue3225-safeguarded, r=graydon
When building Rust libraries (e.g. librustc, libstd, etc), checks for
and verbosely removes previous build products before invoking rustc.
(Also, when Make variable VERBOSE is defined, it will list all of the
libraries matching the object library's glob after the rustc
invocation has completed.)

When installing Rust libraries, checks for previous libraries in
target install directory, but does not remove them.

The thinking behind these two different modes of operation is that the
installation target, unlike the build tree, is not under the control
of this infrastructure and it is not up to this Makefile to decide if
the previous libraries should be removed.

Fixes #3225 (at least in terms of mitigating the multiple library
problem by proactively warning the user about it.)

Diffstat (limited to 'src/rt/rust_kernel.cpp')
0 files changed, 0 insertions, 0 deletions