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

MacPorts noreply at macports.org
Sun Nov 3 10:39:27 UTC 2019


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

 The "Allowed memory size ... exhausted" message is one of the symptoms of
 [https://bugs.php.net/bug.php?id=77284 the PHP bug] we've been talking
 about above, which affects openssl and base64 functions.

 Did your non-`-b` upgrade of php73 to 7.3.11 occur using a binary from our
 server (did you see messages that a tbz2 archive and its rmd160 signature
 was downloaded from packages.macports.org or one of its mirrors) or
 compiled from source on your system (did you see a php-7.3.11.tar.xz
 source file being downloaded, extracted, configured, built, destrooted)?

 The reason why I was asking you to try the binary, and then if it fails to
 try rebuilding from source and attach the log, is that I am operating
 under the suspicion that something about the way we are building our
 binary is not compatible with some users' systems. Our build server uses
 the same MacPorts with the same portfiles to build the binaries, but there
 are of course differences: we deactivate all other ports while building,
 which you don't on your system, so a build from source on your system
 could pick up undeclared dependencies which our build system wouldn't. And
 our build system runs as a virtual machine; that could affect how the php
 build system detects certain characteristics of the system. Comparing your
 from-source build log with ours could help shed light on whether that is
 so.

 The PHP developers have removed the configure-time checks for the SIMD
 functions in PHP 7.4, since there are already runtime checks for them. If
 the problem we're chasing here has to do with possibly incorrect detection
 of something at configure time, then that might fix the problem. I have
 started working on adding php74 to MacPorts so that we can see if it is
 affected too, but several changes were made in the build system that make
 this a little more difficult than previous port updates, so I don't have
 an ETA.

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


More information about the macports-tickets mailing list