Bug #18580: ./configure's log doesn't store stderr, so what's the point?
| From: | ceo at l-i-e dot com | Date: | Fri, 26 Jul 2002 00:03:09 +0000 |
| Subject: | Bug #18580: ./configure's log doesn't store stderr, so what's the point? | ||
| Groups: | php.bugs | ||
| Request: | Send a blank email to php-bugs+get-15250@lists.php.net to get a copy of this message | ||
From: ceo@l-i-e.com
Operating system: Un*x
PHP version: 4.2.1
PHP Bug Type: Feature/Change Request
Bug description: ./configure's log doesn't store stderr, so what's the point?
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 bug report at http://bugs.php.net/?id=18580&edit=1
--
Fixed in CVS: http://bugs.php.net/fix.php?id=18580&r=fixedcvs
Fixed in release: http://bugs.php.net/fix.php?id=18580&r=alreadyfixed
Need backtrace: http://bugs.php.net/fix.php?id=18580&r=needtrace
Try newer version: http://bugs.php.net/fix.php?id=18580&r=oldversion
Not developer issue: http://bugs.php.net/fix.php?id=18580&r=support
Expected behavior: http://bugs.php.net/fix.php?id=18580&r=notwrong
Not enough info: http://bugs.php.net/fix.php?id=18580&r=notenoughinfo
Submitted twice: http://bugs.php.net/fix.php?id=18580&r=submittedtwice
register_globals: http://bugs.php.net/fix.php?id=18580&r=globals