Re: New(!?) warning makes configure for 21.4 break

Mats Lidell writes:

 > I guess we can recommend that work-around to those who get into
 > this!?. Can we hope that 21.5 is stable at the time glibc turn this
 > into an error?

We can certainly declare it "stable" by then.  At current pace, it
won't be stable, though. :-(

 > Note that 21.5 is also affected by these warnings

Of course.

 > but the configure step handles it better there.

I think that's to be expected since autoconf 2.13 was frozen long
before these warnings were even possible :-) while 21.5 uses
up-to-date autoconf (2.59 is a lower bound but I think we actually
require something in the low-to-mid 2.60s).

Steve