-
Notifications
You must be signed in to change notification settings - Fork 298
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
upgrade autoconf on the build machines to version 2.72 #10265
Comments
IMO using autoconf in PATCH looks suspicious. An additional patch can be added in the patchset |
In the patchset, I am patching configure.ac files and then run autoconf in the PATCH function. Should I move that to BUILD instead? I wrote it like this as BUILD shouldn't modify source files, that is what PATCH is for, IMHO. |
Yes.
Generated scripts are not source files. |
I moved the autoconf invocation in texlive_core to BUILD in e2f4699. I leave this open for now because the general issue is still relevant. Although I suppose this can now wait until beta 5 arrives, when an upgrade of the builders is due anyway. The real fix would be the haikuporter improvement mentioned above, to allow anything to be used in PATCH. |
I don't understand why this issue is still open. |
The new texlive 2024 (see #10261) requires autoconf 2.72, and it is used in the PATCH function of texlive_core.
Presumably because of haikuports/haikuporter#168, the version installed on the build host (which is currently 2.71) is used instead of the newer version available in the repository.
The text was updated successfully, but these errors were encountered: