|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #43814 [GCOV] Compile result links for PECL exts
Submitted: 2008-01-11 08:49 UTC Modified: 2021-05-03 12:22 UTC
From: hannes dot magnusson at gmail dot com Assigned:
Status: Open Package: Website problem
PHP Version: Irrelevant OS: Irrelevant
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: hannes dot magnusson at gmail dot com
New email:
PHP Version: OS:


 [2008-01-11 08:49 UTC] hannes dot magnusson at gmail dot com
Links to lxr/cvs are pointing to php-src/ext, even for PECL extensions (example: pecl/phar)...


Add a Patch

Pull Requests

Pull requests:

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2008-01-11 09:12 UTC]
Errr. I mean on the site :)
 [2010-05-03 17:38 UTC]
-Status: Assigned +Status: Feedback
 [2010-05-03 17:38 UTC]
I'm unsure if this problem still exists because PECL extensions moved to core are 
[usually] no longer maintained in PECL, and GCOV only tests core. What do you 

In related news, the links are changed from lxr/cvs to og/svn in SVN.
 [2010-05-03 17:56 UTC] hannes dot magnusson at gmail dot com
-Status: Feedback +Status: Open
 [2010-05-03 17:56 UTC] hannes dot magnusson at gmail dot com
Currently it seems to only do core stuff, but at the time of that writing phar 
was in pecl.
I don't see any pecl extensions there now, but the word is pecl/http will be 
enabled soonish - and it will then have the same problem :)
 [2010-05-03 18:29 UTC]
So extensions that will/may move to core into the future are added? Okay, that 
makes sense, this shouldn't be too difficult. A fix will likely take place once we 
get the official OpenGrok box up and running.
 [2010-05-03 20:31 UTC]
I add new extensions on a per-request basis. This problem only shows up if the extension only lives in PECL.
pecl/http was disabled since it was breaking the build too often, and the authors didn't fix the problem quickly enough. Of course it can be reenabled again if the authors promise they will only commit stuff after (at least) successful compilation.
 [2010-05-07 01:50 UTC]
Nuno, any suggestions for how to fix this bug? In other words, is the information 
(which PECL extensions are enabled) available to site.api.php? Can it be?
 [2010-05-08 22:43 UTC]
The information is not available to the frontend right now.
A "simple" fix is to do a "svn info" on each extensions' dir and check if the url matches pecl or not. Or even have a generic scheme that builds the URL from a generic PHP svn path.
 [2012-06-02 02:08 UTC]
-Status: Assigned +Status: Open -Assigned To: nlopess +Assigned To:
 [2019-09-29 09:21 UTC] Vitalii dot havaretskyi at gmail dot com
The following pull request has been associated:

Patch Name:  Replace http:// to https://
On GitHub:
 [2021-05-03 12:22 UTC]
I think we should decomission, unless somebody is
willing to spend time on making it work with recent PHP version.
The last successful coverage report of PHP 7.4 is from

[1] <>
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Fri Jun 14 19:01:30 2024 UTC