Closed ghost closed 8 years ago
vmod.vcc is used to generate rst files, then rst2man for the manpages IIRCcd
Do you have the latter?
Yes, rst2man is installed and detected by configure
checking build system type... amd64-portbld-freebsd10.1 checking host system type... amd64-portbld-freebsd10.1 checking target system type... amd64-portbld-freebsd10.1 checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... (cached) /bin/mkdir -p checking for gawk... (cached) /usr/bin/awk checking whether gmake sets $(MAKE)... yes checking whether gmake supports nested variables... yes checking for style of include used by gmake... GNU checking for gcc... cc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether cc accepts -g... yes checking for cc option to accept ISO C89... none needed checking whether cc understands -c and -o together... yes checking dependency style of cc... gcc3 checking how to run the C preprocessor... cpp checking for grep that handles long lines and -e... (cached) /usr/bin/grep checking for egrep... (cached) /usr/bin/egrep checking for ANSI C header files... (cached) yes checking for sys/types.h... (cached) yes checking for sys/stat.h... (cached) yes checking for stdlib.h... (cached) yes checking for string.h... (cached) yes checking for memory.h... (cached) yes checking for strings.h... (cached) yes checking for inttypes.h... (cached) yes checking for stdint.h... (cached) yes checking for unistd.h... (cached) yes checking for minix/config.h... (cached) no checking whether it is safe to define __EXTENSIONS__... yes checking for gcc... (cached) cc checking whether we are using the GNU C compiler... (cached) yes checking whether cc accepts -g... (cached) yes checking for cc option to accept ISO C89... (cached) none needed checking whether cc understands -c and -o together... (cached) yes checking dependency style of cc... (cached) gcc3 checking for cc option to accept ISO C99... none needed checking for cc option to accept ISO Standard C... (cached) none needed checking how to run the C preprocessor... cpp checking how to print strings... printf checking for a sed that does not truncate output... (cached) /usr/bin/sed checking for fgrep... (cached) /usr/bin/fgrep checking for ld used by cc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... (cached) 262144 checking how to convert amd64-portbld-freebsd10.1 file names to amd64-portbld-freebsd10.1 format... func_convert_file_noop checking how to convert amd64-portbld-freebsd10.1 file names to toolchain format... func_convert_file_noop checking for /usr/bin/ld option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for dlltool... no checking how to associate runtime and link libraries... printf %s\n checking for ar... ar checking for archiver @FILE support... no checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm -B output from cc object... ok checking for sysroot... no checking for a working dd... /bin/dd checking how to truncate binary pipes... /bin/dd bs=4096 count=1 checking for mt... mt checking if mt is a manifest tool... no checking for dlfcn.h... (cached) yes checking for objdir... .libs checking if cc supports -fno-rtti -fno-exceptions... yes checking for cc option to produce PIC... -fPIC -DPIC checking if cc PIC flag -fPIC -DPIC works... yes checking if cc static flag -static works... yes checking if cc supports -c -o file.o... yes checking if cc supports -c -o file.o... (cached) yes checking whether the cc linker (/usr/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... freebsd10.1 ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... no checking whether gmake sets $(MAKE)... (cached) yes checking for rst2man... rst2man checking for ANSI C header files... (cached) yes checking sys/stdlib.h usability... no checking sys/stdlib.h presence... no checking for sys/stdlib.h... no checking pkg-config is at least version 0.9.0... yes checking for libvarnishapi... yes checking vsha256.h usability... yes checking vsha256.h presence... yes checking for vsha256.h... yes checking cache/cache.h usability... yes checking cache/cache.h presence... yes checking for cache/cache.h... yes checking for python3... /usr/local/bin/python2.7 checking for varnishtest... /usr/local/bin/varnishtest checking for varnishd... /usr/local/sbin/varnishd checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating config.h config.status: executing depfiles commands config.status: executing libtool commands
But "make" or "make install" do not generate/install man pages. Am I missing something?
Not that I can think of.
I will try on FreeBSD 10.3 / varnish 4.1.3 and get back to you.
I can confirm this for fedora/redhat. The manpages build fine by calling rst2man manually, though.
Please build man pages as part of make dist. No need to rebuild these everywhere. Also, rhel5, on which the varnish-modules package builds quite easy, does not include rst2man.
Note that varnish is released this way, with man pages prebuilt in the release tarball.
Ingvar
I've opened a PR to correct this. Not sure how @lkarsten wants to address it though, so I will let him handle it when he's back from holidays.
I have rst2man installed and it is detected by the configure stage, but "make" does not generate the man pages for the modules. I cannot identify a make target that will do this nor a configure option.