[Bug other/12730] New: manual page install broken with old Pod::man

[cgd at broadcom dot com]

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12730

           Summary: manual page install broken with old Pod::man
           Product: gcc
           Version: 3.4
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: other
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: cgd at broadcom dot com
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: mips64-unknown-linux-gnu
  GCC host triplet: mips64-unknown-linux-gnu
GCC target triplet: mips64-unknown-linux-gnu

(this was a native build on mips64-linux-gnu.  Only configure arg
was --prefix=/my/test/dir)

my test system here has an old version of Pod::man.  Configuring
a combined source tree (gcc + binutils + gdb + expect) checked out
w/ date spec -D "2003-10-22 00:00 UTC", a log of the configure/build output
indicates:

configure: warning: 
*** Makeinfo is missing or too old.
*** Info documentation will not be built.
checking for recent Pod::Man... no

Lack of a recent Pod::Man causes GENERATED_MANPAGES in gcc/Makefile to
be set to <nothing>.

When installing manual pages, install-man tries to install (for instance):
$(docobjdir)/gcc.1

However, that file doesn't exist.  Normally it would be generated by
generated-manpages (i.e., GENERATED_MANPAGES would be set to that, and that
would cause the generated man pages to be generated via dependencies).

I'm not sure what The Right Thing here is.  If i had to guess, i'd say it
would be get rid of GENERATED_MANPAGES entirely, and change the rules which
generate the manual pages, e.g.:

$(docobjdir)/%.1: $(docdir)/%.texi stmp-docobjdir
        $(STAMP) $@
        -$(TEXI2POD) $< > $(basename $(notdir $@)).pod
        -($(POD2MAN) --section=1 \
                        $(basename $(notdir $@)).pod > $(@).T$$$$ && \
                mv -f $(@).T$$$$ $@) || \
                (rm -f $(@).T$$$$ && exit 1)
        -rm -f $(basename $(notdir $@)).pod

to do **somethine** useful if POD2MAN is unusable.  From my POV, the best
behaviour would be to copy a preformatted version from the source tree.

Another alternative would be to rearrange the manual page installation targets
to not try to install manual pages that couldn't be built.