RE: why is ./foobar target noted as foobar ??

[Mark Galeck (CW)]

> That is, I'm OK with make recognizing that the strings "./foo" and "foo"
refer to the same file on the disk for the purposes of determining
out-of-dateness etc. but I don't think make should be changing the value
of address@hidden

AMEN.  So, would it get fixed :)  Like I said, I got a Linux kernel break 
precisely due to that.  I may have to follow your advice at
https://savannah.gnu.org/bugs/index.php?10708


>Please don't top-post.

? I am not sure what you mean.  I don't "top-post". Top-posting is where you 
put your reply and then quote the original messages in its entirety below.  I 
don't do that because it is lazy, causes undue network traffic and shows 
disrespect to the reader.  I don't have a particular reply style, I just trim 
and interleave as seems appropriate to get the gist of the reply together with 
that is being replied to.  


> On the other hand, what should make do if it sees two rules like:

./foo: ; @echo with dir
foo: ; @echo without dir


Can you elaborate?


Thank you,

Mark