Am 14. Jänner 2026 01:27:40 MEZ schrieb Dan Wilcox danomatika@gmail.com:
You could try the distribution source tarball from Miller's site which will have the configure script generated
I didn't know that miller is still providing dist tarballs (even when not using git to clone the sources, these days I mostly just grab the tarballs from GitHub...)
in any case: this won't help much, as we are taking about a branch (on top of the last release) that has modifications to the build system (so configure and friends do have to be regenerated)
or do it on a separate machine yourself (not on the SGI) then copy the result over via: make dist
yes that is what needs to be done.
the dependencies to generate the build system are: autoconf, automake & libtool
@Wolfgang you couldn't run autoreconf on the octane (which was kind of expected), but you got "similar errors" on your Linux box. without knowing the actual errors, I guess they were different enough and actually referred to a missing "libtool" installation (which I think is the most common mistake to make).
as forautoreconf vs autogen.sh: the latter is really just a wrapper around the former that has some fallback mechanism to manually call autoconf, automake, aclocal & libtool.
so if you can, you can also just run autoreconf -fiv *instead*.
mfg.sfg.jfd IOhannes