[MacPorts] #58598: PHP 7.3.6 can throw a known bus error on freebsd flavored OS if using ifuncs, can fix in configure.ac

[MacPorts]

#58598: PHP 7.3.6 can throw a known bus error on freebsd flavored OS if using
ifuncs, can fix in configure.ac
----------------------+--------------------
  Reporter:  johnww2  |      Owner:  (none)
      Type:  defect   |     Status:  new
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:  2.5.4
Resolution:           |   Keywords:
      Port:  php73    |
----------------------+--------------------

Comment (by ryandesign):

 Reinstalling a port will reload a launchd plist provided by that port. But
 in the case of php73-apache2handler, it's an Apache module. It doesn't
 itself have a launchd plist. It's the apache2 port that has the launchd
 plist, but MacPorts doesn't know that those two ports are related, so you
 have to restart the service separately.

 At this point I don't know what the culprit is. All three of you reporting
 this problem fixed the problem by rebuilding the port from source (some of
 you by making additional changes, but it's not clear that those changes
 were needed). Everyone reporting the problem has a newer CPU than our
 build machine. In addition, I've [https://bugs.php.net/bug.php?id=78743
 contacted the php developers for help] and they've told me that php will
 double-check the SIMD capabilities at runtime, so even the scenario I
 originally considered—with an older CPU than our build machine's—wouldn't
 be a problem.

 If your ports tree is up to date, you shouldn't even be able to use our
 php binaries—MacPorts should have recognized them as broken and rebuilt
 them already. They were broken by the icu update; I'm working on that; see
 #59439.

 I'm going to try to reproduce this problem on my own Mojave system by
 downgrading the ports tree to before the icu update, so that our binaries
 will work.

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