[MacPorts] #74413: git: build fails on tahoe/arm64 when ld64 installed: tapi error: unknown architecture arm64e.x1-macos

[MacPorts]

#74413: git: build fails on tahoe/arm64 when ld64 installed: tapi error: unknown
architecture arm64e.x1-macos
-------------------------+-------------------------
 Reporter:  mascguy      |      Owner:  herbygillot
     Type:  defect       |     Status:  assigned
 Priority:  Normal       |  Milestone:
Component:  ports        |    Version:  2.12.6
 Keywords:  tahoe arm64  |       Port:  git
-------------------------+-------------------------
 The following occurs when `ld64` (and the appropriate subport) is
 installed on Tahoe/ARM:

 {{{
 ld: multiple errors: tapi error: malformed file
 :info:build
 /Library/Developer/CommandLineTools/SDKs/MacOSX27.0.sdk/System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices.tbd:4:20:
 error: unknown architecture
 :info:build                    arm64e.x1-macos, arm64e.x1-maccatalyst ]
 :info:build                    ^~~~~~~~~~~~~~~

 [...more tapi-related errors...]

 :info:build clang: error: linker command failed with exit code 1 (use -v
 to see invocation)
 :info:build make[1]: *** [contrib/credential/osxkeychain/git-credential-
 osxkeychain] Error 1
 :info:build make: *** [git-credential-osxkeychain] Error 2
 }}}

 Temporarily deactivating `ld64` and `ld64-xcode` solves the issue. But
 that's not a good fix for users in-general.

 Is the `ld64` port outdated, or simply obsolete, for Tahoe/ARM...?

 Of note, `clang-22` depends on `ld64`, so installing the latest Clang
 brings this in. And such was the case on my ARM-based Mac.

 I suppose `git` can declare a build conflict with `ld64`, but is that the
 right approach here...?

-- 
Ticket URL: <https://trac.macports.org/ticket/74413>
MacPorts <https://www.macports.org/>
Ports system for macOS