🚀 go-pugleaf

I have come across a problem with VPATH as implemented by gmake 3.60.
The problem is summerized below.

Two directories...

	/tmp/src1:
	total 6
	-rw-rw-r--   1 brianw   ln1           40 Oct  9 14:56 test.c
	-rw-rw-r--   1 brianw   ln1         1384 Oct  9 14:57 test.o

	/tmp/src2:
	total 36
	-rw-rw-r--   1 brianw   ln1           40 Oct  9 14:55 Makefile
	-rwxrwxr-x   1 brianw   ln1        16384 Oct  9 14:58 test
	-rw-rw-r--   1 brianw   ln1           40 Oct  9 16:58 test.c

Makefile is:


	VPATH= /tmp/src2:/tmp/src1
	test: test.o

and I compile in /tmp/src2 with...

	$ gmake
	gmake: `test' is up to date.

Which, as can be seen, is not true.

src2/test.c is much newer that src2/test and the dependancies are that
test.c should cause the updating of test.o and test.o updates test.

The problem seems to be that once gmake finds a file in the
dependancy list it locks itself into that directory and doesn't use
the viewpath anymore.

I think it should find test.o (in src1) and then discover that test.o is
older that test.c (in src2). Then remake test.o, but make it
in src2, not replace the one in src1 (to which, in the real case here,
I do not have access)

So is it a bug, or do I misunderstand the use of a viewpath?

brian wallis...