[Bug bootstrap/14905] New: 'make install' fails on grepjar.1, not included in tarball

[Bug bootstrap/14905] New: 'make install' fails on grepjar.1, not included in tarball

[mec dot gnu at mindspring dot com]

I'm building gcc 3.4.0-20040406 with pjr's patch for pr gcc/14893.
'make install' fails here:

 /house/chastain/source/gcc-3.4.0-20040406/install-sh -c -m 644 grepjar.1
/tmp/chastain/install/hppa2.0w-hp-hpux11.11/vanilla/target/native/gcc-3.4.0-20040406-as-2.14-ld-vendor/man/man1/grepjar.1
/house/chastain/source/gcc-3.4.0-20040406/install-sh: grepjar.1 does not exist
make[2]: *** [install-man1] Error 1
make[2]: Leaving directory
`/tmp/chastain/build/hppa2.0w-hp-hpux11.11/vanilla/target/native/gcc-3.4.0-20040406-as-2.14-ld-vendor/fastjar'
make[1]: *** [install-am] Error 2
rm jar.pod grepjar.pod
make[1]: Leaving directory
`/tmp/chastain/build/hppa2.0w-hp-hpux11.11/vanilla/target/native/gcc-3.4.0-20040406-as-2.14-ld-vendor/fastjar'
make: *** [install-fastjar] Error 2

The problem is that doc/grepjar.1 is not included in the release tarball.

If perl is available, then 'make bootstrap' will build doc/grepjar.1 from
grepjar.pod.  That's why you don't see this problem on a typical development
system.  If you build gcc 3.4.0-20040406 and look in the build log and search
for 'perl', you can see perl getting executed.  doc/install.texi says that perl
is required for modifying gcc, but not for building gcc.

(Of course I have perl for hpux11.11; but I intentionally bootstrap gcc with a
$PATH that does not include perl).

-- 
           Summary: 'make install' fails on grepjar.1, not included in
                    tarball
           Product: gcc
           Version: 3.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P1
         Component: bootstrap
        AssignedTo: mark at codesourcery dot com
        ReportedBy: mec dot gnu at mindspring dot com
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: native hppa2.0w-hp-hpux11.11
  GCC host triplet: native hppa2.0w-hp-hpux11.11
GCC target triplet: native hppa2.0w-hp-hpux11.11


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14905

[Bug bootstrap/14905] 'make install' fails on grepjar.1, not included in tarball

[mec dot gnu at mindspring dot com]

------- Additional Comments From mec dot gnu at mindspring dot com  2004-04-10 03:01 -------
Created an attachment (id=6070)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=6070&action=view)
gcc-3.4.0-20040406+prj, configure log

I configured with gnu assembler 2.14 and gnu ld 2.14 and --disable-shared.
The exact configuration command is not handy at the moment but I can get it if
you need it.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14905

[Bug bootstrap/14905] 'make install' fails on grepjar.1, not included in tarball

[mec dot gnu at mindspring dot com]

------- Additional Comments From mec dot gnu at mindspring dot com  2004-04-10 03:02 -------
Created an attachment (id=6071)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=6071&action=view)
gcc-3.4.0-20040406+prj, build log.bz2

Compressed build log.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14905

[Bug bootstrap/14905] 'make install' fails on grepjar.1, not included in tarball

[mec dot gnu at mindspring dot com]

------- Additional Comments From mec dot gnu at mindspring dot com  2004-04-10 03:04 -------
Created an attachment (id=6072)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=6072&action=view)
gcc-3.4.0-20040406+prj, install.log

Installation log.
Note the part at the end where 'make' tries to build grepjar.1 because it
doesn't already exist.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14905

[Bug bootstrap/14905] 'make install' fails on grepjar.1, not included in tarball

[mec dot gnu at mindspring dot com]

------- Additional Comments From mec dot gnu at mindspring dot com  2004-04-10 03:06 -------
Errr, I was wrong.  I do have perl in /usr/bin/perl, and I am using it. 
install.log shows that it is running.

There is still some sort of problem at the end of install.log though, where it
tries to build grepjar.1 and fails.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14905

[Bug bootstrap/14905] 'make install' fails on grepjar.1, not included in tarball

[mec dot gnu at mindspring dot 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

[Bug bootstrap/14905] 'make install' fails on grepjar.1, not included in tarball

[kcook at gcc dot gnu dot org]

------- Additional Comments From kcook at gcc dot gnu dot org  2004-04-10 18:21 -------
I'll look in to this

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kcook at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14905

[Bug bootstrap/14905] 'make install' fails on grepjar.1, not included in tarball

[mmitchel at gcc dot gnu dot org]

------- Additional Comments From mmitchel at gcc dot gnu dot org  2004-04-11 19:11 -------
This needs to be fixed before 3.4.0.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |3.4.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14905

[Bug bootstrap/14905] 'make install' fails on grepjar.1, not included in tarball

[mark at codesourcery dot com]

------- Additional Comments From mark at codesourcery dot com  2004-04-11 19:22 -------
Subject: Re:  'make install' fails on grepjar.1, not
 included in tarball

kcook at gcc dot gnu dot org wrote:

>------- Additional Comments From kcook at gcc dot gnu dot org  2004-04-10 18:21 -------
>I'll look in to this
>  
>
It sounds like the Java Makefiles should honor 
--enable-generated-files-in-srcdir for this case, but are failing to do so.



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14905

[Bug bootstrap/14905] 'make install' fails on grepjar.1, not included in tarball

[kcook at gcc dot gnu dot org]

------- Additional Comments From kcook at gcc dot gnu dot org  2004-04-12 10:51 -------
Subject: Re:  'make install' fails on grepjar.1, not included in tarball

The root problem is that POD2MAN is in perl and I never tested the read
only source directory changes on a system without Perl :(

This small hack should fix it by following Mark's suggestion and
recognizing --enable-generated-files-in-srcdir.  Could the bug reporter
try it out, disabling Perl on this system is not an simple task.

Please note that I have only tested this on a 3.5 tree.  Specifically,
I have not yet tried this out with autoconf 2.57 which GCC 3.4 uses,
though I do not expect any difficulties.  I'll do so later today.2004-04-12  Kelley Cook  <kcook@gcc.gnu.org>

	* configure.ac: Recognize --enable-generated-files-in-srcdir.
	* Makefile.am: New rule to copy man files to source directory.
	* configure, Makefile.in: Regenerate.

Index: Makefile.am
===================================================================
RCS file: /cvs/gcc/gcc/fastjar/Makefile.am,v
retrieving revision 1.14
diff -u -p -d -r1.14 Makefile.am
--- Makefile.am	1 Dec 2003 02:58:26 -0000	1.14
+++ Makefile.am	12 Apr 2004 10:34:46 -0000
@@ -67,6 +67,10 @@ fastjar_TEXINFOS = \
 man_MANS = jar.1 grepjar.1
 EXTRA_DIST = $(man_MANS)
 
+if GENINSRC
+man_MANS += stamp-maninsrc
+endif
+
 TEXI2POD = perl $(srcdir)/../contrib/texi2pod.pl
 POD2MAN = pod2man --center="GNU" --release="gcc-@gcc_version@"
 
@@ -74,6 +78,10 @@ POD2MAN = pod2man --center="GNU" --relea
 	-($(POD2MAN) --section=1 $< > $(@).T$$$$ && \
 		mv -f $(@).T$$$$ $@) || \
 		(rm -f $(@).T$$$$ && exit 1)
+
+stamp-maninsrc: jar.1 grepjar.1
+	-cp -p $(top_builddir)/jar.1 $(srcdir)/jar.1
+	-cp -p $(top_builddir)/grepjar.1 $(srcdir)/grepjar.1
 
 .INTERMEDIATE: jar.pod grepjar.pod
 
Index: configure.ac
===================================================================
RCS file: /cvs/gcc/gcc/fastjar/configure.ac,v
retrieving revision 1.2
diff -u -p -d -r1.2 configure.ac
--- configure.ac	11 Mar 2004 00:27:17 -0000	1.2
+++ configure.ac	12 Apr 2004 10:34:48 -0000
@@ -67,6 +67,27 @@ AC_SUBST(ZLIBS)
 AC_SUBST(ZDEPS)
 AC_SUBST(ZINCS)
 
+# GCC LOCAL CHANGE
+# We would like to our source tree to be readonly.  However when releases or
+# pre-releases are generated, the man pages need to be included as they are
+# converted from the texi files via perl which we don't require end users to
+# have installed.
+# Therefore we have --enable-generated-files-in-srcdir to do 
+# just that.
+
+AC_MSG_CHECKING([whether to place generated files in the source directory])
+  dnl generated-files-in-srcdir is disabled by default
+  AC_ARG_ENABLE(generated-files-in-srcdir, 
+[  --enable-generated-files-in-srcdir
+                          put copies of generated files in source dir
+                          intended for creating source tarballs for users
+                          without texinfo bison or flex.],
+      generated_files_in_srcdir=$enableval,
+      generated_files_in_srcdir=no)
+
+AC_MSG_RESULT($generated_files_in_srcdir)
+AM_CONDITIONAL(GENINSRC, test x$generated_files_in_srcdir = xyes)
+
 # Get the version trigger filename from the toplevel
 if test "${with_gcc_version_trigger+set}" = set; then
    gcc_version_trigger=$with_gcc_version_trigger


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14905

[Bug bootstrap/14905] 'make install' fails on grepjar.1, not included in tarball

[kcook34 at ford dot com]

------- Additional Comments From kcook34 at ford dot com  2004-04-12 15:13 -------
Subject: Re:  'make install' fails on grepjar.1, not
 included in tarball [v2]

Take two.

Testing showed that the fastjar.info file also wasn't being put in the 
tarball.

I also didn't like the way that I lied to automake in the first 
iteration; so I dove into the automake documentation and discovered its 
highly useful "all-local:" target.  I think this patch is better.

Now also tested under GCC 3.4 with and without 
--enable-generated-files-in-srcdir.

OK to install?
2004-04-12  Kelley Cook  <kcook@gcc.gnu.org>

	* configure.ac: Parse --enable-generated-files-in-srcdir.
	* Makefile.am: Copy man and info files to srcdir if requested.
	* configure: Regenerate.
	* Makefile.in Regenerate.

diff -prud /home/kcook34/gcc-3.4-20040407/fastjar/Makefile.am ./Makefile.am
--- /home/kcook34/gcc-3.4-20040407/fastjar/Makefile.am	2003-11-30 21:58:26.000000000 -0500
+++ ./Makefile.am	2004-04-12 10:52:36.954084800 -0400
@@ -82,3 +82,26 @@ jar.pod: $(srcdir)/fastjar.texi
 
 grepjar.pod: $(srcdir)/fastjar.texi
 	-$(TEXI2POD) -D grepjar $< > $@
+
+# The following commands allow us to release tarballs with the man pages
+# and info documentation prebuilt.  This feature is enabled via 
+# --enable-generated-files-in-srcdir in the configure script.
+
+if GENINSRC
+STAMP_GENINSRC = stamp-geninsrc
+else
+STAMP_GENINSRC =
+endif
+
+all-local: $(STAMP_GENINSRC) 
+
+stamp-geninsrc: jar.1 grepjar.1 fastjar.info
+	-cp -p $(top_builddir)/jar.1 $(srcdir)/jar.1
+	-cp -p $(top_builddir)/grepjar.1 $(srcdir)/grepjar.1
+	-cp -p $(top_builddir)/fastjar.info $(srcdir)/fastjar.info
+	touch $@
+
+CLEANFILES = stamp-geninsrc
+MAINTAINERCLEANFILES = $(srcdir)/jar.1 \
+                       $(srcdir)/grepjar.1 \
+                       $(srcdir)/fastjar.info
diff -prud /home/kcook34/gcc-3.4-20040407/fastjar/configure.ac ./configure.ac
--- /home/kcook34/gcc-3.4-20040407/fastjar/configure.ac	2004-01-09 21:09:08.000000000 -0500
+++ ./configure.ac	2004-04-12 10:42:02.652003200 -0400
@@ -67,6 +67,26 @@ AC_SUBST(ZLIBS)
 AC_SUBST(ZDEPS)
 AC_SUBST(ZINCS)
 
+# GCC LOCAL CHANGE
+# We would like to our source tree to be readonly.  However when releases or
+# pre-releases are generated, the man pages need to be included as they are
+# converted from the texi files via perl which we don't require end users to
+# have installed.
+# Therefore we have --enable-generated-files-in-srcdir to do just that.
+
+AC_MSG_CHECKING([whether to place generated files in the source directory])
+  dnl generated-files-in-srcdir is disabled by default
+  AC_ARG_ENABLE(generated-files-in-srcdir, 
+[  --enable-generated-files-in-srcdir
+                          put copies of generated files in source dir
+                          intended for creating source tarballs for users
+                          without texinfo, perl, bison or flex.],
+      generated_files_in_srcdir=$enableval,
+      generated_files_in_srcdir=no)
+
+AC_MSG_RESULT($generated_files_in_srcdir)
+AM_CONDITIONAL(GENINSRC, test x$generated_files_in_srcdir = xyes)
+
 # Get the version trigger filename from the toplevel
 if test "${with_gcc_version_trigger+set}" = set; then
    gcc_version_trigger=$with_gcc_version_trigger


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14905

[Bug bootstrap/14905] 'make install' fails on grepjar.1, not included in tarball

[aoliva at redhat dot com]

------- Additional Comments From aoliva at redhat dot com  2004-04-12 17:21 -------
Subject: Re:  'make install' fails on grepjar.1, not included in tarball [v2]

On Apr 12, 2004, Kelley Cook <kcook34@ford.com> wrote:

> +stamp-geninsrc: jar.1 grepjar.1 fastjar.info
> +	-cp -p $(top_builddir)/jar.1 $(srcdir)/jar.1
> +	-cp -p $(top_builddir)/grepjar.1 $(srcdir)/grepjar.1
> +	-cp -p $(top_builddir)/fastjar.info $(srcdir)/fastjar.info

Hmm...  This construct is dangerous.

Consider broken VPATH makes such as Solaris' (yuck).  If the jar.1 dep
resolves to $(srcdir)/jar.1 by VPATH search (which would happen if you
take a release tarball containing the generated doc files), every
occurrence of the jar.1 string in make commands will be replaced with
$(srcdir)/jar.1.  In this case, your construct wouldn't work.

'fraid I don't have any good suggestions on how to work around this
problem.

Hmm...  Maybe we don't have to.  We do require GNU make now, don't we?



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14905

[Bug bootstrap/14905] 'make install' fails on grepjar.1, not included in tarball

[aoliva at redhat dot com]

------- Additional Comments From aoliva at redhat dot com  2004-04-12 17:23 -------
Subject: Re:  'make install' fails on grepjar.1, not included in tarball [v2]

On Apr 12, 2004, Kelley Cook <kcook34@ford.com> wrote:

> Now also tested under GCC 3.4 with and without
> --enable-generated-files-in-srcdir.

Please be sure to test with and without it both with and without the
generated files already in srcdir.

> 	* configure.ac: Parse --enable-generated-files-in-srcdir.
> 	* Makefile.am: Copy man and info files to srcdir if requested.
> 	* configure: Regenerate.
> 	* Makefile.in Regenerate.

Other than the VPATH issue with Solaris make, that we probably don't
have to worry about, it looks ok to me.

BTW, why are you marking the configure.ac changes as GCC LOCAL, but
not the Makefile.am ones?



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14905

[Bug bootstrap/14905] 'make install' fails on grepjar.1, not included in tarball

[kcook at gcc dot gnu dot org]

------- Additional Comments From kcook at gcc dot gnu dot org  2004-04-12 19:37 -------
Subject: Re:  'make install' fails on grepjar.1, not included in tarball [v2]

Alexandre Oliva <aoliva@redhat.com> wrote:
> On Apr 12, 2004, Kelley Cook <kcook34@ford.com> wrote:
> 
> > Now also tested under GCC 3.4 with and without
> > --enable-generated-files-in-srcdir.
> 
> Please be sure to test with and without it both with and without the
> generated files already in srcdir.
> 

I've already done this with GNU make.  Three of them work as expected.

Running a parallel --enable-generated-files-in-srcdir make on a source
directory already containing pregenerated man and info files on a
computer without bison, flex, texinfo, nor perl was a midly interesting
exercise.  Make attempts to copy the sourcedir pregenerated copies to
the sourcedir copies.  cp throws an errors, but due to the "-" in the
make buildrules those errors are ignored.  That seemed like the best
solution in this situation where VPATH bites you.  

Personally, I would think that combination should remain a support-free
option.

> > 	* configure.ac: Parse --enable-generated-files-in-srcdir.
> > 	* Makefile.am: Copy man and info files to srcdir if requested.
> > 	* configure: Regenerate.
> > 	* Makefile.in Regenerate.
> 
> Other than the VPATH issue with Solaris make, that we probably don't
> have to worry about, it looks ok to me.

Over the past few months, I've grown to dislike VPATH.  The concept was
good, but it makes Makefiles very hairy.

> 
> BTW, why are you marking the configure.ac changes as GCC LOCAL, but
> not the Makefile.am ones?

Simple oversight.  I'll add GCC LOCAL to the Makefile.am before
committing.  On the otherhand,  its seems that the upstream of fastjar
is dormant, so maybe the markers are unnecessary.

Mark, OK for 3.4?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14905

[Bug bootstrap/14905] 'make install' fails on grepjar.1, not included in tarball

[cvs-commit at gcc dot gnu dot org]

------- Additional Comments From cvs-commit at gcc dot gnu dot org  2004-04-12 20:30 -------
Subject: Bug 14905

CVSROOT:	/cvs/gcc
Module name:	gcc
Changes by:	kcook@gcc.gnu.org	2004-04-12 20:29:50

Modified files:
	fastjar        : ChangeLog Makefile.am Makefile.in configure 
	                 configure.ac 

Log message:
	2004-04-12  Kelley Cook  <kcook@gcc.gnu.org>
	
	PR bootstrap/14905
	* configure.ac: Parse --enable-generated-files-in-srcdir.
	* Makefile.am: Copy man and info files to srcdir if requested.
	* configure: Regenerate.
	* Makefile.in Regenerate.

Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/fastjar/ChangeLog.diff?cvsroot=gcc&r1=1.63&r2=1.64
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/fastjar/Makefile.am.diff?cvsroot=gcc&r1=1.14&r2=1.15
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/fastjar/Makefile.in.diff?cvsroot=gcc&r1=1.20&r2=1.21
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/fastjar/configure.diff?cvsroot=gcc&r1=1.16&r2=1.17
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/fastjar/configure.ac.diff?cvsroot=gcc&r1=1.2&r2=1.3



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14905

[Bug bootstrap/14905] 'make install' fails on grepjar.1, not included in tarball

[mec dot gnu at mindspring dot com]

------- Additional Comments From mec dot gnu at mindspring dot com  2004-04-13 02:16 -------
It works for me.

I applied the patch in comment #14 to gcc-3.4.0-20040406 and built on native
hppa2.0w-hp-hpux11.11, with no podman.  I put in fake files fastjar/jar.1 and
fastjar/grepjar.1 into the source tree (because they aren't in the first
pre-release tarball).  configure + make bootstrap + make install worked fine.  I
checked the logs and the install tree and they were fine.

Some handy notes:

try "grep -i perl *.log" after a build and see if any extra perl is sneaking in
where it shouldn't.  That doesn't totally catch the differences between cvs
versions and tarball versions though.

If you want to disable perl on a system with perl installed, you could try:

  mkdir $HOME/perl-none
  (echo '#! /bin/sh' ; echo "exit 1") > $HOME/perl-none/perl
  chmod 755 $HOME/perl-none/perl
  PATH=$HOME/perl-none/perl:$PATH
  export PATH



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14905

[Bug bootstrap/14905] 'make install' fails on grepjar.1, not included in tarball

[mmitchel at gcc dot gnu dot org]

------- Additional Comments From mmitchel at gcc dot gnu dot org  2004-04-14 08:04 -------
Please apply this patch to 3.4.0.

Thanks!

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14905

[Bug bootstrap/14905] 'make install' fails on grepjar.1, not included in tarball

[mmitchel at gcc dot gnu dot org]

------- Additional Comments From mmitchel at gcc dot gnu dot org  2004-04-14 08:05 -------
Remove accidental resolution.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|FIXED                       |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14905

[Bug bootstrap/14905] [3.5 Regression] 'make install' fails on grepjar.1, not included in tarball

[pinskia at gcc dot gnu dot org]

------- Additional Comments From pinskia at gcc dot gnu dot org  2004-04-14 23:55 -------
Is this needed for the mainline also so we do not have the same problem when 3.5 (or is it 4.0) gets 
released?

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|FIXED                       |
            Summary|'make install' fails on     |[3.5 Regression] 'make
                   |grepjar.1, not included in  |install' fails on grepjar.1,
                   |tarball                     |not included in tarball
   Target Milestone|3.4.0                       |3.5.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14905

[Bug bootstrap/14905] 'make install' fails on grepjar.1, not included in tarball

[kcook at gcc dot gnu dot org]

------- Additional Comments From kcook at gcc dot gnu dot org  2004-04-14 23:51 -------
Due to check-in, I'm marking the bug as fixed

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14905

[Bug bootstrap/14905] 'make install' fails on grepjar.1, not included in tarball

[cvs-commit at gcc dot gnu dot org]

------- Additional Comments From cvs-commit at gcc dot gnu dot org  2004-04-14 23:49 -------
Subject: Bug 14905

CVSROOT:	/cvs/gcc
Module name:	gcc
Branch: 	gcc-3_4-branch
Changes by:	kcook@gcc.gnu.org	2004-04-14 23:49:37

Modified files:
	fastjar        : ChangeLog Makefile.am Makefile.in configure 
	                 configure.ac 

Log message:
	2004-04-14  Kelley Cook  <kcook@gcc.gnu.org>
	
	PR bootstrap/14905
	* configure.ac: Parse --enable-generated-files-in-srcdir.
	* Makefile.am: Copy man and info files to srcdir if requested.
	* configure: Regenerate.
	* Makefile.in Regenerate.

Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/fastjar/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=1.61&r2=1.61.4.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/fastjar/Makefile.am.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=1.14&r2=1.14.4.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/fastjar/Makefile.in.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=1.20&r2=1.20.4.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/fastjar/configure.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=1.14&r2=1.14.4.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/fastjar/configure.ac.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=1.1&r2=1.1.4.1



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14905

[Bug bootstrap/14905] [3.5 Regression] 'make install' fails on grepjar.1, not included in tarball

[kcook at gcc dot gnu dot org]

------- Additional Comments From kcook at gcc dot gnu dot org  2004-04-15 02:05 -------
See Comment #14 the fix was committed to mainline on Monday

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14905

[Bug bootstrap/14905] [3.4/3.5 Regression] 'make install' fails on grepjar.1, not included in tarball

[pinskia at gcc dot gnu dot org]

------- Additional Comments From pinskia at gcc dot gnu dot org  2004-04-15 02:13 -------
Woops you are right, I must have missed it so closing as fixed.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED
            Summary|[3.5 Regression] 'make      |[3.4/3.5 Regression] 'make
                   |install' fails on grepjar.1,|install' fails on grepjar.1,
                   |not included in tarball     |not included in tarball
   Target Milestone|3.5.0                       |3.4.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14905

[Bug bootstrap/14905] [3.4/3.5 Regression] 'make install' fails on grepjar.1, not included in tarball

[zack at codesourcery dot com]

------- Additional Comments From zack at codesourcery dot com  2004-04-16 17:26 -------
Subject: Re:  'make install' fails on grepjar.1, not
 included in tarball [v2]

Alexandre Oliva <aoliva@redhat.com> writes:

> Hmm...  Maybe we don't have to.  We do require GNU make now, don't we?

I sure thought so.

zw


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14905

[Bug bootstrap/14905] [3.4/3.5 Regression] 'make install' fails on grepjar.1, not included in tarball

[mark at codesourcery dot com]

------- Additional Comments From mark at codesourcery dot com  2004-04-16 17:27 -------
Subject: Re:  'make install' fails on grepjar.1, not
 included in tarball [v2]

Zack Weinberg wrote:

>Alexandre Oliva <aoliva@redhat.com> writes:
>
>  
>
>>Hmm...  Maybe we don't have to.  We do require GNU make now, don't we?
>>    
>>
>
>I sure thought so.
>
Yes, we do.



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14905

[Bug bootstrap/14905] [3.4/3.5 Regression] 'make install' fails on grepjar.1, not included in tarball

[mark at codesourcery dot com]

------- Additional Comments From mark at codesourcery dot com  2004-04-16 17:30 -------
Subject: Re:  'make install' fails on grepjar.1, not
 included in tarball

kcook at gcc dot gnu dot org wrote:

>Mark, OK for 3.4?
>  
>
Yes, thanks.



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14905