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

[MacPorts]

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

Comment (by ryandesign):

 Replying to [comment:23 TheDigitalOrchard]:
 > Would a crash log / stack trace help? Remind me where these logs are
 stored. I've looked in several places, but can't find a recent crash log
 for PHP-FPM.

 Crash logs are in Library/Logs/DiagnosticReports. Which Library depends on
 which user the program ran under. If you start a web server as root, for
 example, it might be /var/root/Library, while if you run under your own
 user, it would be ~/Library. It wouldn't hurt to attach them, though I'm
 pretty sure it'll tell us what we already know.

 > Also, this crashing / memory consumption issue... I'm assuming this
 would only involve the MacPorts version of PHP, which strikes me as odd.

 No, it shouldn't be anything MacPorts-specific, though it may turn out to
 be macOS-version-specific.

 > I run nearly identical installation on many Ubuntu servers, installed
 via apt. It would be disastrous if this problem affected 7.3.11 on this
 other platform. So far I'm not seeing this crash anywhere else, only on my
 local dev Mac. So it's a mystery.

 Ubuntu is Linux, and I haven't heard of this problem affecting Linux. As
 mentioned at the top of this ticket, the problem was reported against
 FreeBSD. They determined that ifuncs are buggy on FreeBSD 11, so they
 disabled their use on FreeBSD. As I said, and as the original reporter
 suggested at the top of this ticket, as a last resort, we can do the same
 on macOS, at the expense of missing out on the optimizations that using
 the SIMD functions were supposed to provide. macOS is after all based on
 BSD, not Linux. But you previously reported that just reinstalling with
 the +debug variant (and not disabling SIMD functions) had solved the
 problem for you at the time, so I had not been convinced that disabling
 the SIMD functions was the right thing to do.

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