On a new system, if you don't install all dependencies the build goes for a bit and then dies with
./autogen.sh: 56: ./autogen.sh: autoreconf: not found
It would be better to check for autoreconf at the beginning of build.sh like other stuff, and tell the user exactly what to install, because the build has no chance of succeeding without this dependency.
On a new system, if you don't install all dependencies the build goes for a bit and then dies with
`
./autogen.sh: 56: ./autogen.sh: autoreconf: not found
`
It would be better to check for `autoreconf` at the beginning of build.sh like other stuff, and tell the user exactly what to install, because the build has no chance of succeeding without this dependency.
On a new system, if you don't install all dependencies the build goes for a bit and then dies with
./autogen.sh: 56: ./autogen.sh: autoreconf: not foundIt would be better to check for
autoreconfat the beginning of build.sh like other stuff, and tell the user exactly what to install, because the build has no chance of succeeding without this dependency.We now check for autoreconf right after checking for cmake in util/build.sh