Branko Čibej <[email protected]> writes: > Using a newer libtool (and autoconf) should not cause problems for users > who build on older platforms, at least most of the time. They're supposed > to be backwards We should make sure however that the release tarballs work > on the current crop: Windows 10+, the various Linux/*BSD/macOS distros not > more than a couple years old. Anyone who builds on really niche platforms > can probably regenerate the build, or use a custom build like Tortoise does. > > For macOS, I can have a go at finding the earliest autoconf and libtool > releases that still work.
That would be very helpful. While this issue doesn't appear to be a regression compared to 1.14.5, I think it's worthwhile to fix the tarball build for macOS. If you can identify the minimum required versions to resolve the problem, I can update our tooling and roll RC3 with them. Another approach would be to use Debian's current stable versions, which are autoconf 2.72 and libtool 2.5.4 [1, 2]. Although making a minimal update focused just on resolving the macOS issue could be safer. > We should also think about upgrading Swig, I found that the generated Ruby > bindings don't work out of the box, either. We currently use the latest Swig 3.x release (3.0.12) when rolling the releases, so an update requires using version 4.x. I think we might want to avoid a major version bump for the 1.15.x release tooling (as far as I understand, this isn't a regression compared to 1.14). But we could probably update to the latest stable Swig 4.x for trunk. [1]: https://packages.debian.org/trixie/autoconf [2]: https://packages.debian.org/trixie/libtool Thanks, Evgeny Kotkov
