@@ -12,7 +12,7 @@ impl TestCx<'_> {
12
12
// For `run-make` V2, we need to perform 2 steps to build and run a `run-make` V2 recipe
13
13
// (`rmake.rs`) to run the actual tests. The support library is already built as a tool rust
14
14
// library and is available under
15
- // `build/$HOST/stage0- bootstrap-tools/$TARGET/release/librun_make_support.rlib`.
15
+ // `build/$HOST/bootstrap-tools/$TARGET/release/librun_make_support.rlib`.
16
16
//
17
17
// 1. We need to build the recipe `rmake.rs` as a binary and link in the `run_make_support`
18
18
// library.
@@ -63,7 +63,7 @@ impl TestCx<'_> {
63
63
//
64
64
// ```
65
65
// build/<target_triple>/
66
- // ├── stage0- bootstrap-tools/
66
+ // ├── bootstrap-tools/
67
67
// │ ├── <host_triple>/release/librun_make_support.rlib // <- support rlib itself
68
68
// │ ├── <host_triple>/release/deps/ // <- deps
69
69
// │ └── release/deps/ // <- deps of deps
@@ -72,7 +72,7 @@ impl TestCx<'_> {
72
72
// FIXME(jieyouxu): there almost certainly is a better way to do this (specifically how the
73
73
// support lib and its deps are organized), but this seems to work for now.
74
74
75
- let tools_bin = host_build_root. join ( "stage0- bootstrap-tools" ) ;
75
+ let tools_bin = host_build_root. join ( "bootstrap-tools" ) ;
76
76
let support_host_path = tools_bin. join ( & self . config . host ) . join ( "release" ) ;
77
77
let support_lib_path = support_host_path. join ( "librun_make_support.rlib" ) ;
78
78
0 commit comments