[Bug bootstrap/14905] 'make install' fails on grepjar.1, not included in tarball
mec dot gnu at mindspring dot com
gcc-bugzilla@gcc.gnu.org
Sat Apr 10 16:19:00 GMT 2004
------- Additional Comments From mec dot gnu at mindspring dot com 2004-04-10 15:47 -------
Here's some more analysis.
In gcc gcc-3_3-branch, fastjar/Makefile.am has this rule:
$(srcdir)/grepjar.1: $(srcdir)/fastjar.texi
-$(TEXI2POD) -D grepjar < $(srcdir)/fastjar.texi > grepjar.pod
-($(POD2MAN) --section=1 grepjar.pod > grepjar.1.T$$$$ && \
mv -f grepjar.1.T$$$$ $(srcdir)/grepjar.1) || \
(rm -f grepjar.1.T$$$$ && exit 1)
-rm -f grepjar.pod
In gcc gcc-3_4-branch, fastjar/Makefile.am has these rules:
%.1: %.pod
-($(POD2MAN) --section=1 $< > $(@).T$$$$ && \
mv -f $(@).T$$$$ $@) || \
(rm -f $(@).T$$$$ && exit 1)
.INTERMEDIATE: jar.pod grepjar.pod
jar.pod: $(srcdir)/fastjar.texi
-$(TEXI2POD) -D jar $< > $@
grepjar.pod: $(srcdir)/fastjar.texi
-$(TEXI2POD) -D grepjar $< > $@
In gcc gcc-3_3-branch, the files jar.1 and grepjar.1 are created in the source
tree. So when a release is made, these files are present in the tarball.
In gcc gcc-3_4-branch, the files jar.1 and grepjar.1 are created in the build
tree. So when a release is made, these files are not present in the tarball.
You can see this by unpacking the pristine tarballs, gcc-3.3.3.tar.bz2 and
gcc-3.4.0-20040406.tar.bz2, and doing "ls -ltr" in the gcc/fastjar/ subdirectory.
So with gcc 3.4.0-20040406, jar.1 and grepjar.1 are built by the user, which
requires perl and pod2man. I have perl installed on my host
(hppa2.0w-hp-hpux11.11), but I don't have pod2man, and that is the failure at
the end of install.log.
This change in fastjar/Makefile.am was made by Kelley Cook on 2003-10-30,
as part of the fix for PR gcc/10996. Have a look at 10996; it's illuminating.
--
What |Removed |Added
----------------------------------------------------------------------------
BugsThisDependsOn| |10996
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14905
More information about the Gcc-bugs
mailing list