[MacPorts] #61170: libffi @3.3_1 fails to build on 10.5 i386

[MacPorts]

#61170: libffi @3.3_1 fails to build on 10.5 i386
-----------------------+--------------------
 Reporter:  fhgwright  |      Owner:  (none)
     Type:  defect     |     Status:  new
 Priority:  Normal     |  Milestone:
Component:  ports      |    Version:  2.6.3
 Keywords:             |       Port:  libffi
-----------------------+--------------------
 The current `libffi` build fails on 10.5 i386, while working in all other
 cases I've tested, including 10.4 ppc/i386, and 10.5 ppc/x86_64.  I
 suspect it has to do with the asm issues noted in the Portfile, with the
 `-integrated-as` option's not being available in this case.  With all
 MacPorts compilers being blacklisted to avoid circular dependencies, and
 the Xcode compilers in older OS versions being gcc, `-integrated-as` isn't
 available.  I was able to get it to build by forcing it to use the already
 installed `clang-7.0`, though that wouldn't work for building from
 scratch.  Note that if it used the same sort of conditional blacklisting
 as in the `libcxx` port, this workaround would have been automatic.

 Since the problem is alleged to relate to the `as` in old versions of
 `cctools`, perhaps using the MacPorts `cctools` would be a fix, but that
 would also have circular dependency problems (except with `+xcode`, but
 that would presumably defeat the purpose).

 It appears that the only thing `llvm` uses `libffi` for is the external
 function interface, which I suspect isn't needed by `clang`.   That
 suggests that a no-frills version of `llvm`, and a `clang` based on it,
 could build `libffi` without circularity.  Splitting `llvm` into `llvm-
 core` and `llvm-extras` could take care of this, and perhaps some other
 questionable dependencies (`ncurses` and `libedit`, really?) as well.

 This port is nomaintainer, but I'm CCing Ken as the last person to touch
 it.

-- 
Ticket URL: <https://trac.macports.org/ticket/61170>
MacPorts <https://www.macports.org/>
Ports system for macOS