[MacPorts] #65910: harfbuzz 5.2 won't compile -- syntax error from mmintrin.h?

[MacPorts]

#65910: harfbuzz 5.2 won't compile -- syntax error from mmintrin.h?
--------------------------------+------------------------
  Reporter:  michael-j-oconnor  |      Owner:  ryandesign
      Type:  defect             |     Status:  assigned
  Priority:  Normal             |  Milestone:
 Component:  ports              |    Version:
Resolution:                     |   Keywords:
      Port:  harfbuzz           |
--------------------------------+------------------------

Comment (by ryandesign):

 Replying to [comment:6 michael-j-oconnor]:
 > I'm surprised that MacPorts buildbots don't use the latest for their OS,
 which is what users are told to run.

 It is the tradeoff that we have so far chosen to use.

 Using the latest Xcode that is compatible with a macOS version will cause
 some ports to fail to build because those port require an SDK that matches
 the OS version, and the latest Xcode that is compatible with a macOS
 version only contains the next major macOS SDK. We do have a MacOSX.sdk
 port which ports could depend on if they needed a specific SDK, but there
 is no support from MacPorts base for doing that so there's a bit of code
 that would need to be added to each portfile to do that so it's a bit
 inconvenient.

 Using the last Xcode that contains the matching SDK causes other ports to
 fail to build, namely those that require a newer compiler. Most of those
 ports are well served by the compiler blacklist mechanism which allows
 MacPorts to install and use a newer compiler. We used to have a problem
 where the compiler blacklist mechanism did not work with ports that build
 using `xcodebuild`. I don't recall whether that is still the case. If so,
 the advantage to our current strategy is that users can overcome the
 problem by building from source on their system after installing the
 latest Xcode, which is typically what users have anyway since that's what
 you get when you install from the App Store. If we instead used the latest
 Xcode on the buildbot workers, users could only work around builds that
 failed due to SDK mismatch with the much more inconvenient step of
 downgrading their Xcode—or we could get around to figuring out how to
 employ the MacOSX.sdk port in those ports that need it.

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