Boris Kolpackov <[EMAIL PROTECTED]> wrote:
RM> Robert Mecklenburg <[EMAIL PROTECTED]> writes:
RM> "Well, bust my buttons!" After creating an empty build.sh.in
RM> autoreconf succeeded in building a configure script. Even running the
RM> ./configure script se
rm> I've checked out the head of the cvs trunk and followed the
rm> instructions in README.cvs but the autoreconf fails:
rm>
rm> autoreconf -i -s
rm> Makefile.am: required file `./README' not found
rm> configure.in:398: required file `build.sh.in' not found
rm> autoreconf: automake failed with exi
I've checked out the head of the cvs trunk and followed the
instructions in README.cvs but the autoreconf fails:
autoreconf -i -s
Makefile.am: required file `./README' not found
configure.in:398: required file `build.sh.in' not found
autoreconf: automake failed with exit status: 1
# This messsage can be executed by make to illustrate my problem.
all: ; @$(call f,a,b)
# The details of macro argument processing aren't clear to me, so I'm
# asking. It appears that all macro arguments are optional, for
# instance:
define g
$1 $2
endef
# The macro g can be called with any n
PDS> Yes. VPATH/vpath is not appropriate for finding targets, only
PDS> for finding source files (that is, files which are not built by
PDS> make but which exist a priori).
PDS>
PDS> See my web site below for a longer description of how VPATH/vpath
PDS> works.
Wow, thanks for the very fast, inf
I apologize in advance if this cross-posting is inappropriate, but it
seemed reasonable at the time...
The following makefile yields two different values for $^ when run
twice in succession:
# Example makefile
vpath %.in /c/work/tmp/src
vpath %.out /c/work/tmp/out
default: stuff/foo.out
if files
aren't found. Thoughts?
Thanks,
--
Robert Mecklenburg
___
Bug-make mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-make
