[MacPorts] #59220: git @ 2.23.0_1 +credential_osxkeychain "unexpected token: !tapi-tbd-v3" - build failure

[MacPorts]

#59220: git @ 2.23.0_1 +credential_osxkeychain "unexpected token: !tapi-tbd-v3" -
build failure
---------------------+----------------------
  Reporter:  bjax    |      Owner:  ci42
      Type:  defect  |     Status:  assigned
  Priority:  Normal  |  Milestone:
 Component:  ports   |    Version:  2.6.1
Resolution:          |   Keywords:
      Port:  git     |
---------------------+----------------------
Changes (by ryandesign):

 * cc: ci42 (removed)
 * status:  new => assigned
 * owner:  (none) => ci42


Comment:

 Replying to [ticket:59220 bjax]:
 > Full variants selected appear to be
 {{{+credential_osxkeychain+diff_highlight+doc+pcre+perl5_26}}} but I only
 asked to {{{port install upgrade outdated}}} when this occurred; I didn't
 specify these variants.
 >
 > I tried uninstalling {{{ld64}}} and reinstalling {{{ld64 +ld64_xcode}}}
 then cleaning and reinstalling {{{git}}} as described in
 comment:ticket:58333:8, but that didn't fix it.
 >
 > I also confirmed {{{xcode-select +p}}} returns
 {{{/Applications/Xcode.app/Contents/Developer}}} as mentioned in several
 older tickets.
 >
 > The "tbd" in the token string seems suspicious...
 >
 > Running MacOSX 10.13.6 with Xcode 10.1.


 "tbd" is not suspicious; it refers to the new "text-based dylib" stub
 files Apple uses in recent SDK versions to
 [https://forums.developer.apple.com/message/9176#9176 save disk space].
 But the linker has to understand them. I'm not sure why yours appears not
 to understand them.

 It builds for me on macOS 10.13.6, but I am using Xcode 9.4.1 with the
 matching command line tools. Using Xcode 10.1, which contains only the
 10.14 SDK and not the 10.13 SDK like Xcode 9 does, may be contributing to
 the problem. Have you installed the command line tools, in addition to
 Xcode? If not, you should. To build things successfully with MacPorts, you
 need an SDK version that matches your OS version, and since you've
 upgraded to an Xcode version that no longer provides that, the command
 line tools are needed. Since your log says
 `DEVELOPER_DIR='/Library/Developer/CommandLineTools'` I assume you do have
 the command line tools installed, but this variable is
 [https://github.com/macports/macports-base/pull/134 new in MacPorts 2.6]
 so I'm just making sure.

 What may be relevant is that the error only occurs as a result of the
 additional building done by the post-build block added by the
 credential_osxkeychain variant; the main building of the port worked fine.
 Maybe one of the environment variables that are set by MacPorts in the
 main build is what allows that to succeed, and the problem may be that the
 custom building in the post-build block does not propagate these
 environment variables. For example, the `DEVELOPER_DIR` variable may be
 relevant.

 The credential_osxkeychain variant is enabled by default but if you don't
 care about the macOS Keychain integration functionality, you could bypass
 the problem by deselecting that variant, which I think can be done with:

 {{{
 sudo port clean git
 sudo port upgrade --enforce-variants git -credential_osxkeychain
 }}}

-- 
Ticket URL: <https://trac.macports.org/ticket/59220#comment:2>
MacPorts <https://www.macports.org/>
Ports system for macOS