public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mec dot gnu at mindspring dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/14905] 'make install' fails on grepjar.1, not included in tarball
Date: Sat, 10 Apr 2004 16:19:00 -0000	[thread overview]
Message-ID: <20040410154743.9362.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040410025940.14905.mec.gnu@mindspring.com>


------- 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


  parent reply	other threads:[~2004-04-10 15:47 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-10  3:06 [Bug bootstrap/14905] New: " mec dot gnu at mindspring dot com
2004-04-10  3:57 ` [Bug bootstrap/14905] " mec dot gnu at mindspring dot com
2004-04-10  4:03 ` mec dot gnu at mindspring dot com
2004-04-10  9:46 ` mec dot gnu at mindspring dot com
2004-04-10 13:02 ` mec dot gnu at mindspring dot com
2004-04-10 16:19 ` mec dot gnu at mindspring dot com [this message]
2004-04-10 19:32 ` kcook at gcc dot gnu dot org
2004-04-11 22:13 ` mmitchel at gcc dot gnu dot org
2004-04-11 22:15 ` mark at codesourcery dot com
2004-04-12 12:51 ` kcook at gcc dot gnu dot org
2004-04-12 15:37 ` kcook34 at ford dot com
2004-04-12 17:47 ` aoliva at redhat dot com
2004-04-12 17:48 ` aoliva at redhat dot com
2004-04-12 20:30 ` kcook at gcc dot gnu dot org
2004-04-12 21:02 ` cvs-commit at gcc dot gnu dot org
2004-04-13  4:17 ` mec dot gnu at mindspring dot com
2004-04-14  9:13 ` mmitchel at gcc dot gnu dot org
2004-04-14 10:07 ` mmitchel at gcc dot gnu dot org
2004-04-15  2:05 ` cvs-commit at gcc dot gnu dot org
2004-04-15  2:05 ` kcook at gcc dot gnu dot org
2004-04-15  2:05 ` [Bug bootstrap/14905] [3.5 Regression] " pinskia at gcc dot gnu dot org
2004-04-15  3:41 ` kcook at gcc dot gnu dot org
2004-04-15  4:08 ` [Bug bootstrap/14905] [3.4/3.5 " pinskia at gcc dot gnu dot org
2004-04-16 17:44 ` zack at codesourcery dot com
2004-04-16 17:46 ` mark at codesourcery dot com
2004-04-16 17:48 ` mark at codesourcery dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040410154743.9362.qmail@sources.redhat.com \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).