2/3/2024 0 Comments Pear note catalina![]() Their conclusion points to using Homebrew (or an equivalent approach) to get a separate version of PHP installed.Īlso My default PHP is enabled. The only real solution to use a custom version of xdebug would be to compile and use you own instance of PHP instead of the build in one. As described here and here, even after signing the binary, MacOS won't allow system binaries to interact with non-system binaries for security reasons. Note that building xdebug from source code and actually trying to use that version of xdebug.so (for example by referencing the built file in xdebug/module/xdebug.so after using make install) with the build-in PHP should end up in a "code signature" error. They refer to Xdebug in the blog post, but this point likely applies to any extension compiled as an. Reading a bit further, the corresponding blog post from the Stack Overflow author suggests that this approach might still pose a problem. If you do attempt to use this solution, the docs for Building the MongoDB PHP Driver from source may be helpful. The apparent solution to that requires modifying the phpize script used by pecl with the new path, as is done in the two links I shared above. The root cause of this issue is Apple removing a standard include path for its bundled version of PHP's headers. this driver, Xdebug, and other PECL packages) are not in a position to address this issue as there is no "installer" within the package to speak of (apart from a Makefile). I'm not sure that going that route will reach a positive outcome, though. If you feel this is a problem with the extension installer, the appropriate place to report that issue would be through and list "PECL" as the "affected package". Just wondering, why should I make changes in OS files? The extension installer files should handle this.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |