Skip to content

Use default Autoconf configuration options checkings (bug #55634) #4348

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

petk
Copy link
Member

@petk petk commented Jul 2, 2019

Instead of building a custom macro for checking configure options, Autoconf 2.62+ outputs a warning at the beginning and the end of the output of configure script. It automatically detects correct and wrong options better.

This is related also to fixing the bug #55634.

Examples:

  • ./configure --with-foo will output warning at the beginning and the end of the ouput

  • ./configure --foo will result in fatal error:

    configure: error: unrecognized option: `--foo'
    Try `./configure --help' for more information
    
  • ./configure --with-foo --enable-option-checking=fatal results in fatal error:

    configure: error: unrecognized options: --with-foo
    

Instead of building a custom macro for checking configure options,
Autoconf 2.62+ outputs a warning at the beginning and the end of the
output of configure script. It automatically detects correct and wrong
options better.

This is related also to fixing the bug #55634.
@petk petk force-pushed the patch-options-checking branch from f8c6713 to 0462cbb Compare July 2, 2019 00:13
Copy link
Member

@nikic nikic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this is even working anymore... I regularly see the autoconf warning, but I don't think I ever saw this "Notice" that we generate.

@php-pulls php-pulls closed this in 16df718 Jul 2, 2019
@petk petk deleted the patch-options-checking branch July 2, 2019 20:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants