Prev |  | Next

## 45. I built NUT from Git, and it complains about lots of missing files. What happened?

If you are not actively developing a driver, can you use a snapshot instead? A NUT CI job generates tar files of the latest NUT source for pull requests and eventual increments of the `master` branch as part of each successful build, and these snapshots include a pre-built version of the `./configure` script. In GitHub build status for each such commit you can see status entries with a "GHA-01: Tarballs" prefix — one of those would have an URL to a ZIP file with a standard source tarball, and another tarball with rendered documentation files.

To build from Git, you will need recent versions of autoconf, automake, libtool, asciidoc, a2x and its dependencies for DocBook/dblatex. Rather than publish a list of the exact versions needed (which will quickly become out of date), we recommend you consult the dependency list in the recipes of your OS distribution for building their official NUT package, and use that as a starting point.

That said, for the numerous systems running build agents of the NUT CI farm, their lists of dependency packages are available in `docs/config-prereqs.txt` in NUT sources.

Prev |  | Next
| Home |