On Tue, 5 Sep 2017 15:50:27 +0200 (CEST)
Jan Engelhardt
On Tuesday 2017-09-05 15:03, Michael Vetter wrote:
The shadow package ships with pre built man pages. However the content of the manpages depends on compile options, which is why I want to built them myself.
However once I remove all the existing man pages, and build with `--enable-man` it stops like this:
``` [ 53s] Making all in cs [ 53s] make[3]: Entering directory '/home/abuild/rpmbuild/BUILD/shadow-4.5/man/cs' [ 53s] make[3]: *** No rule to make target 'man1/expiry.1', needed by 'all-am'. Stop.
man/cs/Makefile.am says "man1/expiry.1", but neither does that file preexist, nor is there any rule in that .am to say how .1 should come into existence.
In other words, not all manpages are generated from something depending on compile options.
So I should not delete the manpages but still use `--enable-man` to generate the ones that can be generated (and are depending on some conditionals)? So even if I only delete login.defs man page (as a test) I get: ``` [ 80s] make[3]: Leaving directory '/home/abuild/rpmbuild/BUILD/shadow-4.5/man/it' [ 80s] Making all in ja [ 80s] make[3]: Entering directory '/home/abuild/rpmbuild/BUILD/shadow-4.5/man/ja' [ 80s] make[3]: *** No rule to make target 'man5/login.defs.5', needed by 'all-am'. Stop. [ 80s] make[3]: Leaving directory '/home/abuild/rpmbuild/BUILD/shadow-4.5/man/ja' ``` So it seems to work for italian but not for japanese? That cannot be intended? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org