Follow-up Comment #5, bug #30323 (project make): Hi Eli,
> Do you have a use-case where argv[0] on Windows does not hold a full file name of Make's executable? Yes. Before the existing code cited in my original post is executed there are two usecases: - Make's executable is found in the PATH env var - Make's executable is found in the current directory After the existing code cited in my original post is executed there's one usecase left: - Make's executable is found in the current directory This is by the way the situation the existing comment cited in my original post refers to: "If it is a name with no slash, we can only hope that PATH did not find it in the current directory." Oliver Schmidt - oliv.schmidt(at)sap.com _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?30323> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/ _______________________________________________ Bug-make mailing list Bug-make@gnu.org http://lists.gnu.org/mailman/listinfo/bug-make