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

MacPorts noreply at macports.org
Mon Dec 30 00:11:52 UTC 2024


#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 fhgwright):

 Replying to [comment:9 hardincj]:
 > OK - a lot of comments overnight - let me try to answer some of the
 questions.
 >
 [...]
 > 4.  I had checked the build status page mentioned above, and noted that
 while the port health entries are mostly green, the entry for 'Sequoia
 (ARM64)' shows up as '?'. That was part of the reason I chose to submit
 the ticket - it looked like it hadn't been tested yet.

 I imagine that ''all'' 'Sequoia (ARM64)' entries are '?', given that
 there's no buildbot for 'Sequoia (ARM64)'.  The buildbot landscape for
 arm64 is deficient at both ends of the OS scale.

 It builds fine for that configuration here, including `+universal`.  It
 doesn't pass its tests,
 which is in general par for the course for `libffi`, but in this case the
 main problem is a known bug in `dejagnu`.

 > All that said, I took Ryan's original advice and just ran 'sudo port
 clean libffi', and then re-ran a normal install. The install ran clean
 with no errors, so I think we can close this ticket. I'm just guessing,
 but it seems likely that some remnant from before the migration was
 causing the previous problems. Once it was cleaned out, everything seems
 OK. Thank you very much for the help.

 Maybe there's an arch-related bug in `port migrate`, though it's not clear
 how reproducible it is.

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


More information about the macports-tickets mailing list