remove "build/host" symlink

This seems like an overkill. We can still document things consistently without
needing to create a symlink for it. Something like "build/$host-target-triple/stage2"
should be clear enough.

Signed-off-by: onur-ozkan <work@onurozkan.dev>

src/bootstrap/src/lib.rs

@@ -37,9 +37,7 @@ use crate::core::builder;
 use crate::core::builder::{Builder, Kind};
 use crate::core::config::{DryRun, LldMode, LlvmLibunwind, Target, TargetSelection, flags};
 use crate::utils::exec::{BehaviorOnFailure, BootstrapCommand, CommandOutput, OutputMode, command};
-use crate::utils::helpers::{
-    self, dir_is_empty, exe, libdir, mtime, output, set_file_times, symlink_dir,
-};
+use crate::utils::helpers::{self, dir_is_empty, exe, libdir, mtime, output, set_file_times};
 
 mod core;
 mod utils;
@@ -470,23 +468,6 @@ impl Build {
             crate::core::metadata::build(&mut build);
         }
 
-        // Make a symbolic link so we can use a consistent directory in the documentation.
-        let build_triple = build.out.join(build.build);
-        t!(fs::create_dir_all(&build_triple));
-        let host = build.out.join("host");
-        if host.is_symlink() {
-            // Left over from a previous build; overwrite it.
-            // This matters if `build.build` has changed between invocations.
-            #[cfg(windows)]
-            t!(fs::remove_dir(&host));
-            #[cfg(not(windows))]
-            t!(fs::remove_file(&host));
-        }
-        t!(
-            symlink_dir(&build.config, &build_triple, &host),
-            format!("symlink_dir({} => {}) failed", host.display(), build_triple.display())
-        );
-
         build
     }