php.net |  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: -
Votes:1
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
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please — but make sure to vote on the bug!
Your email address:
MUST BE VALID
Solve the problem:
48 - 46 = ?
Subscribe to this entry?

 
 [2011-08-19 12:12 UTC] 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.

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

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 
it
 
PHP Copyright © 2001-2019 The PHP Group
All rights reserved.
Last updated: Sat Nov 16 21:01:32 2019 UTC