On 2022/08/20 23:42:26 +0100, Thomas Adam <thomas@xteddy.org> wrote:
> On Sat, 20 Aug 2022 at 23:13, Omar Polo <op@omarpolo.com> wrote:
> > Thomas mentioned on irc that we could probably avoid this by using a
> > newer autoconf, but as far as i can see there's only 2.69 (and
> > 2.13???) on void linux.
> 
> Should be fixed on the 'linux' branch, if you could try that?

(sorry for the delay)

Yes!  It works now, thanks! :)

[op@philae got-portable]$ ./autogen.sh
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not using Libtool
autoreconf: running: /usr/bin/autoconf --force
autoreconf: configure.ac: not using Autoheader
autoreconf: running: automake --add-missing --copy --force-missing
autoreconf: Leaving directory `.'
[op@philae got-portable]$ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking build system type... aarch64-unknown-linux-gnu
checking host system type... aarch64-unknown-linux-gnu
checking for gcc... gcc
checking whether the C compiler works... yes
...