[MacPorts] #66871: Installation on Leopard broken? Error: The installed version of Xcode (3.1.4) is too old to use on the installed OS version. Version 14.2 or late is recommended

MacPorts noreply at macports.org
Tue Feb 28 07:24:42 UTC 2023


#66871: Installation on Leopard broken? Error: The installed version of Xcode
(3.1.4) is too old to use on the installed OS version. Version 14.2 or late
is recommended
---------------------------+------------------------------
  Reporter:  barracuda156  |      Owner:  (none)
      Type:  defect        |     Status:  new
  Priority:  Normal        |  Milestone:
 Component:  base          |    Version:  2.8.1
Resolution:                |   Keywords:  leopard, powerpc
      Port:                |
---------------------------+------------------------------

Comment (by ryandesign):

 Replying to [comment:7 Traace]:
 > I wonder why MACOSX_DEPLOYMENT_TARGET is empty

 The default value of `MACOSX_DEPLOYMENT_TARGET` is based on the value of
 `macos_version_major`; if the latter isn't being determined properly of
 course the former won't be either.

 https://github.com/macports/macports-
 base/blob/9c8da9d61008249ea51e130d7ea02cb2177799ad/src/macports1.0/macports.tcl#L1219-L1225

 What model Mac are you seeing this problem on, and does it have a working
 built-in Ethernet interface? My recollection now (this is from memory) is
 that my QEMU VM presented itself as a computer without built-in Ethernet,
 and an Ethernet card, but macOS uses the MAC address of the built-in
 Ethernet interface to compute the Mac's UUID. When it fails to find a
 built-in Ethernet interface, the message `_CFGetHostUUIDString: unable to
 determine UUID for host. Error: 35` is printed by a whole lot of programs,
 including `sw_vers`, which was what was throwing MacPorts off in my case.
 I suspected MacPorts was trying to interpret that message along with the
 version output. While that one instance of the problem could be corrected,
 I suspected similar problems would affect other code in MacPorts or in
 ports' build systems so I didn't bother. The problem went away once I
 tricked macOS into thinking it had a built-in Ethernet interface.

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


More information about the macports-tickets mailing list