Bug #55462 [Opn->Fbk]: './buidconf --force' doesn't work anymore with symlinked extensions

Edit report at https://bugs.php.net/bug.php?id=55462&edit=1 ID: 55462 Updated by: cmb@php.net Reported by: saltwaterc at gmail dot com Summary: './buidconf --force' doesn't work anymore with symlinked extensions -Status: Open +Status: Feedback Type: Bug Package: *Compile Issues Operating System: Debian squeeze PHP Version: 5.3.7 -Assigned To: +Assigned To: cmb Block user comment: N Private report: N New Comment: Is this still an issue with any of the actively supported PHP versions[1]? It is certainly not an issue on Windows. [1] <https://www.php.net/supported-versions.php> Previous Comments: ------------------------------------------------------------------------ [2011-09-04 18:41:23] php at richud dot com update- copied contents of /build folder from 5.2.7 over top of 5.3.8 and fixed it ------------------------------------------------------------------------ [2011-09-04 17:47:18] php at richud dot com Have same problem with 5.3.8 and APC (not symlinked) ------------------------------------------------------------------------ [2011-08-19 12:12:36] saltwaterc at gmail dot com Description: ------------ Till PHP 5.3.6 one could used symlinked directories for embedding certain extensions into a PHP build. Example: php-5.3.6/ext/apc -> /path/to/APC-3.1.9 php-5.3.7/ext/apc -> /path/to/APC-3.1.9 In the first case (5.3.6) ./buildconf --force used to rebuild the configuration. In the second case (5.3.6) it does nothing. There aren't any fs permission issues. That's the first thing that I checked. Test script: --------------- Symlink an external extension into the ext directory. Run ./buildconf --force. Expected result: ---------------- Reconfiguration in order to expose the new extension to the configure script. Actual result: -------------- Nothing relevant. ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=55462&edit=1