|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #55462 './buidconf --force' doesn't work anymore with symlinked extensions
Submitted: 2011-08-19 12:12 UTC Modified: -
Avg. Score:3.0 ± 0.0
Reproduced:1 of 1 (100.0%)
Same Version:0 (0.0%)
Same OS:0 (0.0%)
From: saltwaterc at gmail dot com Assigned:
Status: Open Package: *Compile Issues
PHP Version: 5.3.7 OS: Debian squeeze
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
Block user comment
Status: Assign to:
Bug Type:
From: saltwaterc at gmail dot com
New email:
PHP Version: OS:


 [2011-08-19 12:12 UTC] saltwaterc at gmail dot com
Till PHP 5.3.6 one could used symlinked directories for embedding certain 
extensions into a PHP build.


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.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2011-09-04 17:47 UTC] php at richud dot com
Have same problem with 5.3.8 and APC (not symlinked)
 [2011-09-04 18:41 UTC] php at richud dot com
update- copied contents of /build folder from 5.2.7 over top of 5.3.8 and fixed 
PHP Copyright © 2001-2021 The PHP Group
All rights reserved.
Last updated: Thu May 06 21:01:24 2021 UTC