This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Patch to generate gcov manpage
- To: Zack Weinberg <zackw at stanford dot edu>
- Subject: Re: Patch to generate gcov manpage
- From: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- Date: Sun, 19 Nov 2000 23:07:54 +0000 (GMT)
- cc: <gcc-patches at gcc dot gnu dot org>
On Sun, 19 Nov 2000, Zack Weinberg wrote:
> > +TEXI2POD = $(srcdir)/../contrib/texi2pod.pl
> > +POD2MAN = pod2man --center="GNU" --release="gcc-$(version)" --section=1
>
> Needs to be predicated on the existence of Perl and pod2man. And
> therefore we need to continue shipping gcov.1 etc with release
> bundles.
The patch to gcc_update should mean that this is of no concern to users
(who use gcc_update --touch; if not they'll already be running into such
problems as needing the right version of autoconf etc.). I don't think
that such maintainer-only rules need predication any more than rules that
run gperf need it.
> Not safe in the presence of simultaneous builds from the same
> directory. You need
How about the following?
@@ -2165,6 +2167,13 @@
texindex cpp.??
TEXINPUTS=${texidir}:$(srcdir):$$TEXINPUTS tex cpp.texi
+$(srcdir)/gcov.1: $(srcdir)/gcov.texi
+ $(TEXI2POD) < $(srcdir)/gcov.texi > gcov.pod
+ ($(POD2MAN) gcov.pod > $(srcdir)/gcov.1.T$$$$ && \
+ mv -f $(srcdir)/gcov.1.T$$$$ $(srcdir)/gcov.1) || \
+ (rm -f $(srcdir)/gcov.1.T$$$$ && exit 1)
+ rm -f gcov.pod
+
#
# Deletion of files made during compilation.
# There are four levels of this:
--
Joseph S. Myers
jsm28@cam.ac.uk