On Sun, Oct 11, 2026 at 04:11:38PM +0000, Werner LEMBERG wrote: > > [bb73e1a8f545699395ad38aba1d591605d00db6f] > > I've just called > > ``` > git clean -fdx > ./autogen.sh > ./configure > make -j12 > ``` > > and `make` aborted because it couldn't find `gperf`. Is this > expected? If compilation from the tarball doesn't need this program, > maybe the `configure` script could be adjusted to abort if it detects > a compilation directly from git and `gperf` is missing.
It is expected. In README-hacking, in 'Development tools', there is: You'll also need ... gperf (for building "unicase/*" and "uninorm/*" modules from gnulib). It should not be needed from the tarball. I am not sure that having different tests for tarball and version control code is a needed complexity. Developpers building from git should know thay they should read README-hacking when something goes wrong, I think. -- Pat
