Branko Čibej <[email protected]> writes: > I "fixed" this by rerunning autogen.sh on the extracted tarball, but that's > not a good solution.
Do you happen to know if this issue also occurs with any of our previous tarballs, such as 1.14.5? > Right now I have no idea what's different, except that the latest libtool > works differntly enough from whichever version was used to create the > release. Mine is > > $ /opt/homebrew/bin/glibtool --version > glibtool (GNU libtool) 2.5.4 For context, the version used to roll this tarball was libtool 2.4.6, which was prepared as part of the `release.py build-env` step [1]. [1]: https://svn.apache.org/viewvc/subversion/trunk/tools/dist/release-lines.yaml?revision=1933378&view=markup#l22 Thanks, Evgeny Kotkov
