Skip to content

Commit 51ae5d0

Browse files
authored
Rollup merge of #64148 - guanqun:typo-fix, r=zackmdavis
fix a few typos in comments
2 parents a0f0a96 + 8e06724 commit 51ae5d0

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/librustc_llvm/build.rs

+3-3
Original file line numberDiff line numberDiff line change
@@ -54,15 +54,15 @@ fn main() {
5454
// LLVM are compiled the same way, but for us that's typically the case.
5555
//
5656
// We *want* detect this cross compiling situation by asking llvm-config
57-
// what it's host-target is. If that's not the TARGET, then we're cross
57+
// what its host-target is. If that's not the TARGET, then we're cross
5858
// compiling. Unfortunately `llvm-config` seems either be buggy, or we're
5959
// misconfiguring it, because the `i686-pc-windows-gnu` build of LLVM will
6060
// report itself with a `--host-target` of `x86_64-pc-windows-gnu`. This
6161
// tricks us into thinking we're doing a cross build when we aren't, so
6262
// havoc ensues.
6363
//
6464
// In any case, if we're cross compiling, this generally just means that we
65-
// can't trust all the output of llvm-config becaues it might be targeted
65+
// can't trust all the output of llvm-config because it might be targeted
6666
// for the host rather than the target. As a result a bunch of blocks below
6767
// are gated on `if !is_crossed`
6868
let target = env::var("TARGET").expect("TARGET was not set");
@@ -166,7 +166,7 @@ fn main() {
166166

167167
let (llvm_kind, llvm_link_arg) = detect_llvm_link();
168168

169-
// Link in all LLVM libraries, if we're uwring the "wrong" llvm-config then
169+
// Link in all LLVM libraries, if we're using the "wrong" llvm-config then
170170
// we don't pick up system libs because unfortunately they're for the host
171171
// of llvm-config, not the target that we're attempting to link.
172172
let mut cmd = Command::new(&llvm_config);

0 commit comments

Comments
 (0)