shadow - autoconf wizards needed

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

shadow - autoconf wizards needed

Michael Vetter
Hi,

I am looking for some autoconf and maybe docbook wizards.

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.
```
For complete log and package see:
https://build.opensuse.org/package/live_build_log/home:jubalh:branches:Base:System/shadow/openSUSE_Factory/x86_64

I looked at all the involved Makefiles but didn't find the reason for
this.

https://github.com/shadow-maint/shadow/blob/master/man/Makefile.am
https://github.com/shadow-maint/shadow/blob/master/man/generate_mans.mak

Probably
https://github.com/shadow-maint/shadow/blob/master/man/generate_translations.mak
is more interesting since it only seems to happen for translated ones.

On this note, I saw that
https://github.com/shadow-maint/shadow/tree/master/man/po actually only
has few translations present.

But looking at generate_translations.mak I still think it shouldn't
matter. Not sure I understand it well enough though.

Maybe some autoconf guru can help?

cheers,
Michael
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: shadow - autoconf wizards needed

Andreas Schwab-2
On Sep 05 2017, Michael Vetter <[hidden email]> wrote:

> [   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.
> ```
> For complete log and package see:
> https://build.opensuse.org/package/live_build_log/home:jubalh:branches:Base:System/shadow/openSUSE_Factory/x86_64
>
> I looked at all the involved Makefiles but didn't find the reason for
> this.

I don't see any rules in man/cs/Makefile.am that generate the manpages.

Andreas.

--
Andreas Schwab, SUSE Labs, [hidden email]
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: shadow - autoconf wizards needed

Jan Engelhardt-4
In reply to this post by Michael Vetter

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.
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: shadow - autoconf wizards needed

Michael Vetter
On Tue, 5 Sep 2017 15:50:27 +0200 (CEST)
Jan Engelhardt <[hidden email]> wrote:

> 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: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: shadow - autoconf wizards needed

Andreas Schwab-2
On Sep 05 2017, Michael Vetter <[hidden email]> wrote:

> So it seems to work for italian but not for japanese?

it/Makefile.am contains rules, ja/Makefile.am doesn't.  Related,
po/it.po exists, po/ja.po doesn't.

Andreas.

--
Andreas Schwab, SUSE Labs, [hidden email]
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]