[MacPorts] #61568: pinentry-mac @0.9.4 has still problems to build on Big Sur

[MacPorts]

#61568: pinentry-mac @0.9.4 has still problems to build on Big Sur
---------------------------+----------------------
  Reporter:  ballapete     |      Owner:  Ionic
      Type:  defect        |     Status:  assigned
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.6.4
Resolution:                |   Keywords:  bigsur
      Port:  pinentry-mac  |
---------------------------+----------------------

Comment (by ryandesign):

 Replying to [comment:7 mascguy]:
 > Replying to [comment:6 svalgaard]:
 > > After running Xcode with GUI for the first time, where it asks me to
 allow it to install "additional components", the installation succeeds.
 >
 > Given that this fix works for both macOS 10.12 and Big Sur, are we 100%
 certain that the `HOME` environment variable is the sole issue?

 I do not know that that fixes the problem for both 10.12 and 11.x. I do
 not know whether the 10.12 and 11.x issues reported here are the same. I
 do know that xcodebuild does not respect the HOME environment variable (or
 did not, the last time I checked) and that this causes us some problems on
 macOS 10.14 and later. This problem does not affect earlier systems so it
 would not have been the cause of whatever was wrong on 10.12.

 I just tried a new build on 10.12 and it worked:
 https://build.macports.org/builders/ports-10.12_x86_64-builder/builds/144992

 We already had successful builds on 10.8 and later, excluding 10.12 but
 including 11.x.

 > Ryan, do you know whether the Xcode IDE has been launched at least once,
 within each of our builders? If not, would it be feasible to do this, as
 annoying as that prospect is?

 It is certainly my intention to always launch Xcode once every time I
 install or update Xcode on the buildbot workers. This ensures the license
 agreement is agreed to and the additional components are installed. The
 additional components are for iOS/iPadOS/watchOS/tvOS development so
 they're of no interest to MacPorts but I figured I should do it since
 Xcode expects them to be there. Maybe I forgot to do it once?


 > Port reports on Big Sur that Xcode is not correctly installed. This
 seems to be a bug in port IMO.

 The warning that MacPorts 2.6.4 emits that the 11.2 SDK is not installed
 is a MacPorts bug, in that we assumed that an SDK matching the OS version
 should always exist, but that turned out not to be true. This assumption
 is fixed in MacPorts 2.7.0 of which a beta is out now.

 The warning that some ports emit that the Xcode command line tools are not
 installed is not a MacPorts bug; it is a macOS bug. See ProblemHotlist
 #reinstall-clt.

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