Bug #18580 Updated: ./configure's log doesn't store stderr, so what's the point?
| From: | sniper@php.net | Date: | Fri, 26 Jul 2002 00:42:25 +0000 |
| Subject: | Bug #18580 Updated: ./configure's log doesn't store stderr, so what's the point? | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-15255@lists.php.net to get a copy of this message | ||
ID: 18580
Updated by: sniper@php.net
Reported By: ceo@l-i-e.com
-Status: Open
+Status: Bogus
Bug Type: Feature/Change Request
Operating System: Un*x
PHP Version: 4.2.1
New Comment:
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.
Previous Comments:
------------------------------------------------------------------------
[2002-07-25 20:03:08] ceo@l-i-e.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
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=18580&edit=1