public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug other/12730] New: manual page install broken with old Pod::man
@ 2003-10-22 18:23 cgd at broadcom dot com
  2003-10-22 18:31 ` [Bug other/12730] " cgd at broadcom dot com
                   ` (10 more replies)
  0 siblings, 11 replies; 13+ messages in thread
From: cgd at broadcom dot com @ 2003-10-22 18:23 UTC (permalink / raw)
  To: gcc-bugs

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

\x18Lack 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.


^ permalink raw reply	[flat|nested] 13+ messages in thread
[parent not found: <bug-12730-4013@http.gcc.gnu.org/bugzilla/>]

end of thread, other threads:[~2006-02-20 14:48 UTC | newest]

Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-10-22 18:23 [Bug other/12730] New: manual page install broken with old Pod::man cgd at broadcom dot com
2003-10-22 18:31 ` [Bug other/12730] " cgd at broadcom dot com
2003-10-22 18:32 ` cgd at broadcom dot com
2003-10-23 19:30 ` kcook at gcc dot gnu dot org
2004-01-15  5:10 ` [Bug other/12730] [3.4 Regression] " pinskia at gcc dot gnu dot org
2004-01-15 14:40 ` kcook at gcc dot gnu dot org
2004-01-19 23:16 ` [Bug other/12730] [3.4/3.5 " kcook at gcc dot gnu dot org
2004-01-21  2:02 ` cvs-commit at gcc dot gnu dot org
2004-01-21  2:14 ` [Bug other/12730] [3.4 " pinskia at gcc dot gnu dot org
2004-01-21  4:01 ` cvs-commit at gcc dot gnu dot org
2004-01-21  4:16 ` pinskia at gcc dot gnu dot org
2004-01-27 13:05 ` cvs-commit at gcc dot gnu dot org
     [not found] <bug-12730-4013@http.gcc.gnu.org/bugzilla/>
2006-02-20 14:48 ` bonzini at gnu dot org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).