Bug #55634 [Opn]: ./configure does not fail if invalid option is used
| From: | cmb@php.net | Date: | Thu, 15 Sep 2016 14:08:59 +0000 |
| Subject: | Bug #55634 [Opn]: ./configure does not fail if invalid option is used | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-204065@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=55634&edit=1
ID: 55634
Updated by: cmb@php.net
Reported by: cweiske@php.net
Summary: ./configure does not fail if invalid option is used
Status: Open
Type: Bug
Package: *Configuration Issues
PHP Version: 5.3.8
Block user comment: N
Private report: N
New Comment:
On Windows, configure bails out early if an unknown option is
passed, what I find rather helpful.
Previous Comments:
------------------------------------------------------------------------
[2013-08-02 11:57:32] mike@php.net
It's not always been like that, there have been times where configure ignored
unknown arguments silently. So, I'd say, we're open for improvements.
------------------------------------------------------------------------
[2011-09-22 19:09:58] pajoye@php.net
well, I do consider it as a bug fix.
------------------------------------------------------------------------
[2011-09-22 19:07:27] ashnazg@php.net
Perhaps a BC compromise here would be to at least *also* echo to stderr, while leaving the existing
echo to stdout in place?
------------------------------------------------------------------------
[2011-09-07 22:28:17] fa@php.net
I'm not saying this behaviour is wrong or right, I've been bitten by this already myself,
but I do think that could be considered a BC break, as I remember it always being like that,
although I'm only 100% sure on 5.2+
------------------------------------------------------------------------
[2011-09-07 13:17:55] cweiske@php.net
Description:
------------
When using ./configure --with-foo, configure tells me at the end:
> Notice: Following unknown configure options were used:
> --with-foo
There are two problems:
- This problem is echoed to stdout, not stderr where capturing it would be possible
- The exit code is still 0, although I clearly issued a wrong option.
In the end I cannot figure out if the configure run was *fully* successful.
Expected result:
----------------
1. config option errors echoed to stderr
2. exit code of configure script != 0
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=55634&edit=1