Bug #55634 [Opn->Wfx]: ./configure does not fail if invalid option is used
Edit report at https://bugs.php.net/bug.php?id=55634&edit=1
ID: 55634
Updated by: petk@php.net
Reported by: cweiske@php.net
Summary: ./configure does not fail if invalid option is used
-Status: Open
+Status: Wont fix
Type: Bug
Package: *Configuration Issues
PHP Version: 5.3.8
Block user comment: N
Private report: N
New Comment:
Helo, instead of building a custom macro for checking configure options, Autoconf 2.62+ already
outputs a warning at the beginning and the end of the output of configure script. It automatically
detects correct and wrong options better.
So now instead a better way is the default Autoconf approach:
This outputs a warning at the beginning and end of the configure output:
./configure --with-non-existing
This results in fatal error:
./configure --non-existing
configure: error: unrecognized option: `--non-existing'
Try `./configure --help' for more information
The --enable-option-checking=fatal results in fatal error for all non existing options:
./configure --with-non-existing --enable-option-checking=fatal
configure: error: unrecognized options: --with-non-existing
Applied to PHP-7.4+. Hope this helps more now.
Thank you for reporting issues and helping make PHP better.
Previous Comments:
------------------------------------------------------------------------
[2019-07-02 00:09:27] petk@php.net
The following pull request has been associated:
Patch Name: Use default Autoconf configuration options checkings (bug #55634)
On GitHub: https://github.com/php/php-src/pull/4348
Patch: https://github.com/php/php-src/pull/4348.patch
------------------------------------------------------------------------
[2016-09-15 14:08:58] cmb@php.net
On Windows, configure bails out early if an unknown option is
passed, what I find rather helpful.
------------------------------------------------------------------------
[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?
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=55634
--
Edit this bug report at https://bugs.php.net/bug.php?id=55634&edit=1
Thread (8 messages)