Hello.
While trying to implement a kind of memoization of lazy macros in GNU make
(needed for my work on Automake-NG), I've been encountering some strange
failure in GNU make (present in all of 3.80, 3.81, 3.82). Here is the
minimal reproducer I've been able to find:
mufoofoo = \
x
Stefano,
This is a bug, and it has been described and fixed here:
https://savannah.gnu.org/patch/?7534
2012/5/12 Stefano Lattarini
> Hello.
>
> While trying to implement a kind of memoization of lazy macros in GNU make
> (needed for my work on Automake-NG), I've been encountering some strange
On 05/12/2012 04:41 PM, Eldar Abusalimov wrote:
> Stefano,
>
> This is a bug, and it has been described and fixed here:
> https://savannah.gnu.org/patch/?7534
>
Thank you very much for the reference. Too bad this bug will prevent
me from using the lazy-evaluation trick with any GNU make < 3.83 :
On 05/12/2012 05:21 PM, Stefano Lattarini wrote:
> On 05/12/2012 04:41 PM, Eldar Abusalimov wrote:
>> Stefano,
>>
>> This is a bug, and it has been described and fixed here:
>> https://savannah.gnu.org/patch/?7534
>>
> Thank you very much for the reference. Too bad this bug will prevent
> me from
I've been trying to put together a non-recursive build system and ran into
the fact that gmake's "include" directive is always relative to the CWD.
This isn't how cpp does things, and is unexpected behavior to say the least.
Is there some unavoidable reason why relative includes aren't relative to
