[PATCH] Drop GNU make 3.80 compatibility

2011-04-01 Thread Kevin Cernekee
The "$(and" operator requires GNU make 3.81. On 3.80 it is a no-op. Consequently, strange build problems (failure to compile madvise.c) pop up when using make 3.80. Since nobody else is reporting these types of problems, I'm going to guess that I am one of the last remaining holdouts still runnin

Re: [PATCH] Drop GNU make 3.80 compatibility

2011-04-01 Thread Mike Frysinger
On Fri, Apr 1, 2011 at 11:23 AM, Kevin Cernekee wrote: > The "$(and" operator requires GNU make 3.81.  On 3.80 it is a no-op. > Consequently, strange build problems (failure to compile madvise.c) pop > up when using make 3.80. > > Since nobody else is reporting these types of problems, I'm going to

Re: [PATCH] Drop GNU make 3.80 compatibility

2011-04-01 Thread Kevin Cernekee
On Fri, Apr 1, 2011 at 1:43 PM, Mike Frysinger wrote: > On Fri, Apr 1, 2011 at 11:23 AM, Kevin Cernekee wrote: >> The "$(and" operator requires GNU make 3.81.  On 3.80 it is a no-op. >> Consequently, strange build problems (failure to compile madvise.c) pop >> up when using make 3.80. >> >> Since

Re: [PATCH] Drop GNU make 3.80 compatibility

2011-04-08 Thread Khem Raj
On Fri, 2011-04-01 at 14:24 -0700, Kevin Cernekee wrote: > On Fri, Apr 1, 2011 at 1:43 PM, Mike Frysinger wrote: > > On Fri, Apr 1, 2011 at 11:23 AM, Kevin Cernekee wrote: > >> The "$(and" operator requires GNU make 3.81. On 3.80 it is a no-op. > >> Consequently, strange build problems (failure t

Re: [PATCH] Drop GNU make 3.80 compatibility

2011-04-09 Thread Kevin Cernekee
On Fri, Apr 8, 2011 at 5:34 PM, Khem Raj wrote: > I think it would be nice to keep it working with make 3.80 even though > its 10 years old. Are these problems widespread ? if not then consider > cooking up a patch :) Done. There is one more occurrence in the link.asneeded function (Rules.mak) w