Hello,
I had two problems with job.c, and consider them bugs, at least the
second one. (I admit I don't quite understand what was going on in
the first case.)
The problems were with construct_command_argv_internal() when supplied
a large LINE argument consisting of many lines. My system:
[2
You <[EMAIL PROTECTED]> wrote:
your post contains some incorrect statements about how and why the
problem occurs, and also incorrect implications for the fix.
Well, make's code is not easy to debug (deep recursion), and I have
not done this before. I certainly do not see all the issues eve
You <[EMAIL PROTECTED]> wrote:
Your fix is not correct; note that the documentation for $(eval ...)
says:
The result of the `eval' function is always the empty string;
thus, it can be placed virtually anywhere in a makefile without
causing syntax errors.
Thus, there is no
Hello!
Given this input:
f0 = $(foreach s,foobar,$(firstword $s:))
e0 = $(foreach s,foobar,$(eval $s:))
f1 = $(foreach s,foobar, $(firstword $s:))
e1 = $(foreach s,foobar, $(eval $s:))
f2 = $(foreach s,foobar, $(firstword $s:))
e2 = $(foreach s,foobar, $(eval $s:))
all:
Paul Smith wrote in this list (April 30, 2001):
GNU Make uses a directory cache in order to speed up processing.
Because of this cache, once the directory is read it will only be
seen (from within make) to contain changes that make knows about
I think this should be mentioned in the
[03:48:40] toomas@ns:~ $ make $$$ fast
make: *** No rule to make target `31061$'. Stop.
[03:48:43] toomas@ns:~ $
___
Bug-make mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-make
