[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH 4/4] Use AM_MISSING_PROG when making bison the default YACC h

From: Bruno Haible
Subject: Re: [PATCH 4/4] Use AM_MISSING_PROG when making bison the default YACC here
Date: Wed, 28 Apr 2010 02:05:04 +0200
User-agent: KMail/1.9.9

Daniel Richard G. wrote:
> Timestamps were not the problem. The native make(1) worked fine (i.e.
> did not try to invoke $(YACC)) when building inside the source tree.

> For my part, if I've fiddled with a .y file, and $(YACC) doesn't work,
> then a build failure is a given. The problem here appears to come down
> to make(1) not handling the dependencies correctly, since it doesn't do
> VPATH and it's building outside of the source tree.

This is not a supported way of building GNU packages. Citing doc/INSTALL.UTF-8
from gnulib:

     You can compile the package for more than one kind of computer at the
  same time, by placing the object files for each architecture in their
  own directory.  To do this, you can use GNU ‘make’.  ‘cd’ to the
  directory where you want the object files and executables to go and run
  the ‘configure’ script.  ‘configure’ automatically checks for the
  source code in the directory that ‘configure’ is in and in ‘..’.  This
  is known as a "VPATH" build.

     With a non-GNU ‘make’, it is safer to compile the package for one
  architecture at a time in the source code directory.  After you have
  installed the package for one architecture, use ‘make distclean’ before
  reconfiguring for another architecture.

If you can build a package with non-GNU make in builddir = srcdir,
and with GNU make in builddir != srcdir, that's all we promise.

If, in order to so support building with non-GNU make in builddir != srcdir,
you can propose a small change to the Makefile.am, that will be fine with
us. But making the builds less reliable, like Andreas proposed by use of
the 'missing' program, is IMO not adequate.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]