https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201523
--- Comment #14 from Kubilay Kocak ---
Removing the option for LIBFFI is a workaround. It's preferable the root cause
is addressed. Since no-one addressed the reproduction/isolation questions in
comment 6 (the reason this is still an open i
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201523
Kubilay Kocak changed:
What|Removed |Added
Status|In Progress |Open
--- Comment #15 from Kubilay
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213812
Kubilay Kocak changed:
What|Removed |Added
Flags|merge-quarterly?|merge-quarterly+
--
You are recei
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209551
Kubilay Kocak changed:
What|Removed |Added
CC||ko...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201523
--- Comment #16 from Chris Rees ---
I must admit I still think we should just remove the LIBFFI option.
The best solution in my opinion is to have it as an amd64 option only,
especially as it's a transient problem, and upstream clearly doe
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201523
Kubilay Kocak changed:
What|Removed |Added
Flags||merge-quarterly?
Statu
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you
