Re: Make: Issue with $(MAKE) in make includes, when make is not on the default path

[Thomas Wolff <towo@towo.net>]

Am 24/10/2022 um 11:36 schrieb marco atzeri:
> On Sun, Oct 23, 2022 at 7:27 PM Ferenc Valenta <ferenc.valenta@gmail.com> wrote:
>>
>> Hi,
>>
>> Just found a possible issue with Cygwin:
>> If cygwin is not on the default path, and make is started by specyfing
>> the path to it (e.g., c:\cygwin64\bin\make), $(MAKE) works in the
>> top-level makefile, but it does not work in make includes.
>> To reproduce the issue, use these files:
>>
>> makefile:
>> $(info $(shell $(MAKE) --version))
>> include test.mak
>>
>> test.mak:
>> $(info $(shell $(MAKE) --version))
>>
>> Make sure that Cygwin is not on the default path, e.g. type *path ;* to
>> erase the default path entirely.
>> Then start make by specifying the path to it: c:\cygwin64\bin\make
>>
>> The first $(MAKE) call works, the second one does not.
>> If make is on the default path, both work.
>>
>> Best regards,
>>
>> --
>> Ferenc Valenta / System Architect / Mentor Graphics Deutschland
This works as expected when calling /bin/make or C:/cygwin64/bin/make ;
the problem is the backslash notation.

>
> Hi Ferenc,
>
> I doubt this should be considered a specific Cygwin bug or a bug at all
>
> Marco
>