4 ms·
One of the worst things about Autoconf is the way it is deployed in the GNU Project's own programs. Typically, GNU project programs assume that anyone working
by kazinator 3y ago
One of the worst things about Autoconf is the way it is deployed in the GNU Project's own programs.
Typically, GNU project programs assume that anyone working on the program (cloning the repo, looking for bugs, making changes, ...) has the Autotools installed. Not just any Autotools but the exact version the program wants.
Only the "release tarball" if a GNU program contains the generated ./configure script that can run on a machine that doesn't have Autotools installed. You have to do some "make boostrap".
So to make a source code release, they can't just tag a code baseline and serve that; they have to generate the release source!
See the stupidity? The source code that is being released has to be compiled from the real source source.
Now this makes life hell if you have to, say, git bisect to find a commit that introduces a problem. To be sure you're building each bisect step correctly, you have to disclean everything and re-run the autoconf bootstrapping, then ./configure and so on. The old code you're checking out may call for different Autotools versions from the trunk head.
Working with some GNU programs is basically hell.
- NoGravitas 3y agoEverything you say is technically true, but I can't remember a time when just having the latest autotools from my distribution packages wasn't sufficient to build a GNU package.
- kazinator 3y agoThat's either a lucky coincidence, or use of a pre-generated ./configure script, not Autotools. If you're actually running the steps to regenerate the Makefile.in from Makefile.am, and configure from configure.ac, and all that, then you run into the version or version range checks. For instance, I have working repo of GNU Make. In the generate Makefile there are lines like: AUTOMAKE = ${SHELL} /home/kaz/make/build-aux/missing automake-1.16 The generated script missing is a wrapper for the program such as automate-1.16, which prints an error if it is missing. This version requirement comes from the file boostrap.conf: # Build prerequisites buildreq="\ autoconf 2.69 automake 1.16.1 " These prereuisite versions are also mentioned in configure.ac: AC_PREREQ([2.69]) # [ ... ] AM_INIT_AUTOMAKE([1.16.1 foreign -Werror -Wall]) Literally, the Autotools source is asserting it must be processed by a certain version of the tools. Needless to say, these lines change in the git history.