Tinyproxy's Man Pages Have Their Own Build Requirement

A Tinyproxy configure failure mentioning a manual-page generator is a build prerequisite check. It occurs before the installed proxy can listen for requests.

The source tree matters. Older build recipes mention AsciiDoc and a2x. The current upstream configure source checks for pod2man when man-page support is enabled and the distribution does not already contain generated manuals.

For a source tree with that supported option, a build that intentionally omits local man pages can be configured with:

./configure --disable-manpage-support

Check the options of the exact source version being built. Disabling documentation does not select a proxy port or alter HTTP forwarding policy; it changes which build products are requested.

If manuals are required, supply the generator expected by that version or use its release distribution with generated pages where provided. The upstream README also distinguishes a Git checkout, which needs the project's bootstrap step, from a release tarball containing a configure script.

Prefer the supported configure option to deleting a docs entry from a generated Makefile. Regenerating the build files can replace that manual edit, while the configure choice records the intended build.