Auto merge of rust-lang#138250 - jieyouxu:ios-mitigation, r=<try>

[WIP] Use `/usr/bin/strip` on macOS -> iOS cross as a temporary mitigation

Mitigation for <rust-lang#138212>. This reintroduces the "hard-coded strip" workaround (but only for iOS) that was initially introduced in rust-lang#130781.

Looks like LLVM 20's initial `llvm-objcopy` version that we ship as `rust-objcopy` may be producing stripped iOS binaries with invalid offsets that fail iOS platform consistency checks.

For the time being, use macOS system strip at `/usr/bin/strip` which should be available (unlike Linux -> macOS cross where this is not guaranteed to be available, partially why we are shipping `llvm-objcopy` in the first place[^linux-darwin-cross]) that shouldn't have this offset problem.

### Review and testing advice

I don't have access to either macOS or iOS platforms, and I can't really write a test for this. This will need to be tested manually.

r? `@davidtwco` (or reroll)
cc *-apple-ios target maintainers `@badboy` `@deg4uss3r` `@madsmtm`

try-job: dist-apple-various
try-job: dist-x86_64-apple

[^linux-darwin-cross]: rust-lang#131206

Author: bors

compiler/rustc_codegen_ssa/src/back/link.rs

@@ -1046,7 +1046,15 @@ fn link_natively(
     let strip = sess.opts.cg.strip;
 
     if sess.target.is_like_osx {
-        let stripcmd = "rust-objcopy";
+        let stripcmd = if sess.target.os == "ios" {
+            // FIXME(#138212): properly fix `llvm-objcopy` upstream when stripping iOS binaries
+            // (seemingly producing stripped binaries with incorrect offsets that fail platform
+            // consistency checks).
+            "/usr/bin/strip"
+        } else {
+            "rust-objcopy"
+        };
+
         match (strip, crate_type) {
             (Strip::Debuginfo, _) => {
                 strip_with_external_utility(sess, stripcmd, out_filename, &["--strip-debug"])