[MacPorts] #71668: libffi @3.4.6; Build Failure

[MacPorts]

#71668: libffi @3.4.6;  Build Failure
-----------------------+-----------------------
  Reporter:  hardincj  |      Owner:  fhgwright
      Type:  defect    |     Status:  assigned
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:  2.10.5
Resolution:            |   Keywords:
      Port:  libffi    |
-----------------------+-----------------------

Comment (by ryandesign):

 Replying to [comment:3 fhgwright]:
 > Presumably if the relevant terminal/shell were a universal build, then
 this wouldn't happen.

 Not necessarily. The user may have deliberately told the terminal to open
 in Rosetta. See #71080 for one previous instance of that; there have been
 others.

 > Aside from the apparent architecture screwup, if there's a problem with
 `libffi` on `x86_64`, that's a bug, anyway, but first-order, it looks like
 just a problem with architecture fickleness.

 As far as I know there isn't a general problem building libffi for x86_64
 on x86_64 nor on arm64 for arm64 (based on the all-green
 [https://ports.macports.org/port/libffi/details/ build status] of libffi,
 [ticket:71602 if that page will load for you]), but there may be a problem
 cross-compiling some ports like libffi for arm64 on x86_64, which is
 effectively what's happening here. MacPorts ''should'' support cross-
 compiling but in many cases like this it doesn't work well. Users will
 encounter a better experience by not attempting to cross-compile.

 > It would also be helpful if base did a better job of supporting Rosetta-
 based setups.

 Josh already added several accommodations for Rosetta-based setups in
 recent MacPorts base versions, which surprised me because I don't think we
 should be encouraging the practice.

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