This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Bootstrap failure building fastjar/jar.1, missing pod2man
- From: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- To: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- Cc: <tromey at redhat dot com>, <gcc-bugs at gcc dot gnu dot org>, <gcc at gcc dot gnu dot org>, <java at gcc dot gnu dot org>
- Date: Sun, 22 Sep 2002 19:15:22 +0100 (BST)
- Subject: Re: Bootstrap failure building fastjar/jar.1, missing pod2man
On Sun, 22 Sep 2002, Kaveh R. Ghazi wrote:
> Correct, I don't get the problem in the gcc directory. However I
> don't understand what's different in order to fix it. Can you (or
> someone else) help figure this out?
There is a configure check
# Is pod2man recent enough to regenerate manpages?
AC_MSG_CHECKING([for recent Pod::Man])
if (perl -e 'use 1.10 Pod::Man') >/dev/null 2>&1; then
AC_MSG_RESULT(yes)
GENERATED_MANPAGES=generated-manpages AC_SUBST(GENERATED_MANPAGES)
else
AC_MSG_RESULT(no)
GENERATED_MANPAGES=
fi
in gcc/configure.in. Then the dependency causing manpages to be built is
on $(GENERATED_MANPAGES) = @GENERATED_MANPAGES@ (and generated-manpages
depends on lang.generated-manpages, putting the language pages under the
same control).
It's desirable for this check to be centralised somewhere. Likewise the
check for makeinfo version should be centralised, and apply to the fastjar
manual as well (the manual may only require 4.0 now and so not cause
problems, but when we move to using @copying as recommended in the Texinfo
4.2 release notes to be done "as soon as possible", a lot more people may
not have that version).
--
Joseph S. Myers
jsm28@cam.ac.uk