# The rustbuild feature thread

**URL:** <https://internals.rust-lang.org/t/the-rustbuild-feature-thread/3643>\
**Category:** tools and infrastructure\
**Created:** [July 1, 2016, 11:10pm UTC](https://internals.rust-lang.org/t/the-rustbuild-feature-thread/3643 "2016-07-01T23:10:28Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![petrochenkov](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/petrochenkov/32/2784_2.png) [@petrochenkov](https://internals.rust-lang.org/u/petrochenkov)\
**Post date:** [September 22, 2016, 8:20am UTC](https://internals.rust-lang.org/t/the-rustbuild-feature-thread/3643/19 "2016-09-22T08:20:17Z")

</div>

Ok, question number two 🙂

How to mark a target as “done”? Suppose a run-pass target fails on my machine due to a rustc/test/whatever bug (e.g. [this](https://github.com/rust-lang/rust/pull/36264#issuecomment-248420143)). With the old build system I can `touch tmp/x86-64-blah-blah-blah-rpass.ok` and then build remaining targets, what is the rustbuild equivalent? Spurious (a la “can’t write directory”) or persistent failures almost always happen on Windows, so this is a blocker.

Also, why are targets named “steps”? And how to know which targets depend on which? E.g. how do I know if `check` runs `tidy` or not? With makefiles it was obvious, with rustbuild the dependencies must be _somewhere_ in the source code, but I haven’t read the `bootstrap` code carefully yet. (Also, what is the equivalent of `make check-notidy`?)

---

_[View the full topic](https://internals.rust-lang.org/t/the-rustbuild-feature-thread/3643)._