-
-
Notifications
You must be signed in to change notification settings - Fork 30.9k
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
Missing definition in configure.ac causing autoreconf to create damaged configure script #87783
Comments
The problem In the repository, the definition for
The solution It appears a file was missing in the m4/ directory. The file matches this one from the Autoconf Archive: https://www.gnu.org/software/autoconf-archive/ax_check_compile_flag.html Simply adding the correct m4 file to m4/ should make |
I never used autoreconf. If you don't run it, ./configure works fine. I only use "autoconf" and "autoheader". $ ./configure --enable-optimizations --enable-shared
(...)
$ grep semantic Makefile
CONFIGURE_CFLAGS_NODIST= -fno-semantic-interposition -std=c99 -Wextra -Wno-unused-result -Wno-unused-parameter -Wno-missing-field-initializers -Werror=implicit-function-declaration -fvisibility=hidden
CONFIGURE_LDFLAGS_NODIST= -fno-semantic-interposition |
From the configure.ac file:
I take it to mean "if configure.ac is changed, run autoreconf first", and that's what I did. Could you let me know what is the intended way to modify configure.ac and have it take effect? |
Ah, maybe the configure.ac comment should be updated to suggest running "autoconf" instead ;-) |
The extra macros are provided by optional packages. On Fedora and Debian/Ubuntu the package is called autoconf-archive. |
Thank you very much. This (and the patch) is clearing things up for me a lot. At first I thought I was supposed to copy the m4 files over from the autoconf archive into the m4 directory under the repo. |
Thanks for the bug report! I ran into the issue a couple of weeks ago on one machine that had autoconf but not the archive package installed. |
Hmm, I've seen this accomplished elsewhere using m4_pattern_forbid, which would make autoreconf fail with the following message:
Example patch attached. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: