[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