Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 09/09/2012 02:05 PM, Tom Lane wrote:
>> And the answer is ... it's a gmake bug.
> Thanks for pursuing this. Whether or not it masks the underlying
> problem, it's still something we should do, no? In fact, it seems to me
> like this makes it even less worth trying to do anything better.
Yeah, exactly.
regards, tom lane