-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
regen autotools related files #77667
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
There are few if any functional changes, but this is helpful when making other changes to the build system. |
If these changes are autogenerated, I would prefer that a trusted core developer create a PR. Is it safe to bump the minimal required version of autotools to 2.69? This can prevent building Python on conservative systems. |
They are fully auto-generated (using autoupdate and autoreconf). It someone else wants to submit the PR, feel free.
This should only affect rerunning autoreconf and related tools. It won't affect the use of "configure" (and therefore "make") which is checked into the repository. |
I got the same changes in configure.ac. |
If we are going to bump the tools version from 2.65 to 2.69 for master, we should probably bump them for all active branches. It creates confusion and makes backporting more difficult. Besides, it appears that, at the moment, the checked-in configure files for 3.7, 3.6, and 2.7 were all generated with 2.69 anyway :) if doing so, the reference to 2.65 in the devguide setup.rst should also be updated. |
Hi Ned, thanks for this clarification |
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: