[MacPorts] #58598: php73: can throw a known bus error on freebsd flavored OS if using ifuncs, can fix in configure.ac (was: PHP 7.3.6 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    |
----------------------+------------------------
Changes (by ryandesign):

 * cc: TheDigitalOrchard (added)


Comment:

 I've updated the php ports. If you `sudo port selfupdate` you'll have the
 update available. Specifically, the php73 ports are now at 7.3.11_0.

 To help us isolate the cause of this problem and hopefully fix it, it
 would be helpful if anyone who was experiencing the issue would update to
 php73 @7.3.11_0 using the binaries we compiled to see if they still have
 the problem. I haven't done anything to fix the problem, so I expect you
 will still experience it.

 To ensure you get our binary, use the `-b` flag when updating, i.e. `sudo
 port -b upgrade outdated`. Not all ports have binaries available. If you
 encounter a non-php73 port that won't upgrade using a binary (or
 php73-apache2handler if you're using that, since we have no binaries for
 that either), `sudo port upgrade ...` that port alone, then go back to
 `sudo port -b upgrade outdated` until you successfully upgrade the php73
 ports. Then you can upgrade any remaining ports using `sudo port upgrade
 outdated` if needed.

 If php73 won't upgrade using a binary, make sure you're using the default
 variants. If you're using different variants, temporarily try using the
 default variants, for example by reinstalling the port without specifying
 variants, e.g. `sudo port -b install php73`.

 If you're using php in a web server environment, remember to restart the
 web server. If you're using php73-fpm, the launchd plist in the port
 should restart FPM when the port upgrades, but if you're not using that
 launchd plist, remember to restart your FPM processes.

 -----

 Assuming you encounter the problem with a binary of 7.3.11_0, then please
 try rebuilding the affected ports from source and keeping the log file.
 You can rebuild using the `-n` and `--force` flags; you can ensure it's
 from source using the `-s` flag; you can keep the log using the `-k` flag.
 So for example: `sudo port -nsk upgrade --force php73` to rebuild php73
 from source and keep the log. Please do this for just one port at a time,
 then retest. If it still happens, try rebuilding another affected port.
 Which ports are affected? php73 probably, php73-openssl maybe, and if
 you're using a different SAPI (php73-apache2handler, php73-cgi,
 php73-fpm), then that SAPI maybe. Retest after each rebuild, remembering
 to restart the web server or FPM if applicable.

 My hope is that after rebuilding one of these ports, it will work again.
 Assuming that happens, please attach your log files from your builds to
 this ticket. The log file's location is printed by running e.g. `port
 logfile php73`. We can then compare your logs with those from our build
 machine to see if there's a difference.

 Our build logs:\\
 [https://build.macports.org/builders/ports-10.14_x86_64-builder/builds/44266
 php73]\\
 [https://build.macports.org/builders/ports-10.14_x86_64-builder/builds/44351
 php73-apache2handler]\\
 [https://build.macports.org/builders/ports-10.14_x86_64-builder/builds/44353
 php73-cgi]\\
 [https://build.macports.org/builders/ports-10.14_x86_64-builder/builds/44358
 php73-fpm]\\
 [https://build.macports.org/builders/ports-10.14_x86_64-builder/builds/44372
 php73-openssl]

 And of course let us know if I'm guessing wrong—if you don't see the
 problem anymore even with our 7.3.11 binaries, or if you're not able to
 fix the problem by rebuilding from source. (In the latter case, you
 [wiki:howto/InstallingOlderPort can go back to the previous version].)

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