|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Request #18580 ./configure's log doesn't store stderr, so what's the point?
Submitted: 2002-07-25 20:03 UTC Modified: 2002-07-25 20:42 UTC
From: ceo at l-i-e dot com Assigned:
Status: Not a bug Package: Feature/Change Request
PHP Version: 4.2.1 OS: Un*x
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: ceo at l-i-e dot com
New email:
PHP Version: OS:


 [2002-07-25 20:03 UTC] ceo at l-i-e dot com
I know all y'all geeks can just read config.cache, but for 
us mere mortals who can't quite grok that, config.log would 
be *MUCH* more useful if it also contained stderr output, so 
that instead of seeing:

Checking for blahblah...

We'd see

Checking for blahblah... No

And maybe even some of the error messages that tell us why 
we didn't get no blahblah even though we asked for it.

I find myself doing:
./configure ... 2&>1 config.output &
all the time, but I gotta figure you guys could just do that 
automatically so config.log has all that.

Apologies if this made it into 4.2.2 which I ain't got yet.  
(I'm behind a firewall and nobody but can surf to me anyway, 
so it's not a critical upgrade just


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2002-07-25 20:42 UTC]
Sorry, but this is not possible.
After all, we are developing PHP not autoconf here..better ask them autoconf people for this kind of feature?

And reading config.log is not really that hard. If test succeeds, there are no error lines below it..if it doesn't
succeed, there is some messages telling why the test failed.

PHP Copyright © 2001-2022 The PHP Group
All rights reserved.
Last updated: Sat May 28 18:05:45 2022 UTC