Re: Path to binary in --help or --version

%% "J. Grant" <[EMAIL PROTECTED]> writes: >> I'm not sure how you imagine this would work, or what use it would >> be. If you run --version don't you already know that you have >> different versions? jg> For instance, cygwin make ver 3.80 and msys/mingw make ver 3.80, jg> both installe

Re: Path to binary in --help or --version

Hi, I'm not sure how you imagine this would work, or what use it would be. If you run --version don't you already know that you have different versions? For instance, cygwin make ver 3.80 and msys/mingw make ver 3.80, both installed, and used by different build processes. However, there are pro

Re: Path to binary in --help or --version

%% "J. Grant" <[EMAIL PROTECTED]> writes: jg> One problem I have frequently come across is having multiple jg> incompatible versions of make installed. jg> This would be solved if the path was visible. Could the path to jg> the binary being run be added to the --help or --version output

Path to binary in --help or --version

Hi, One problem I have frequently come across is having multiple incompatible versions of make installed. This would be solved if the path was visible. Could the path to the binary being run be added to the --help or --version output please? Alternatively if I submit a patch to add this will it b

Re: target-specific appending with an empty value

Hi, the following patch corrects the described bug, i.e. the makefile === Makefile Begin == a = 1 targ: a += targ: @echo "$@: a = $(a)" === Makefile End === gives now the correct answer: "targ: a = 1". Best Regards, Oliver Index: expand.c ===