-
Notifications
You must be signed in to change notification settings - Fork 7.9k
buildconf warning with autoconf 2.71 #9483
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
Comments
Looks like everything apart from AC_PROG_CC_C99 is part of libtool.m4. |
#8514 was an attempt to deal with this IIRC |
Girgias
pushed a commit
that referenced
this issue
Jan 23, 2023
To make sure that compiler supports C99 before Autoconf 2.69, this was needed. But with Autoconf 2.70 and later the macro is obsolete because the checks are done in AC_PROG_CC and warnings are emitted when building configure script. Fixes part of GH-9483
petk
added a commit
to petk/php-src
that referenced
this issue
May 8, 2023
Please cherry-pick both commits to 8.2 at least as after packaging (for Alpinelinux) this errors pollute logs of every build of PECL packages |
andypost
pushed a commit
to skilld-labs/php-src
that referenced
this issue
May 19, 2023
To make sure that compiler supports C99 before Autoconf 2.69, this was needed. But with Autoconf 2.70 and later the macro is obsolete because the checks are done in AC_PROG_CC and warnings are emitted when building configure script. Fixes part of phpGH-9483
andypost
pushed a commit
to skilld-labs/php-src
that referenced
this issue
May 19, 2023
petk
added a commit
to petk/php-src
that referenced
this issue
Jul 5, 2023
Co-authored-by: Levi Morrison <morrison.levi@gmail.com>
ramsey
pushed a commit
that referenced
this issue
Jul 10, 2023
Co-authored-by: Levi Morrison <morrison.levi@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Running
./buildconf
with autoconf 2.71 (Ubuntu 22.04) results in a slew of warnings:PHP Version
PHP 8.3
Operating System
Ubuntu 22.04
The text was updated successfully, but these errors were encountered: